Micro-services architecture to integrate heterogeneous nodes for digital feed generation

ABSTRACT

Example implementations include a system to present opportunities from third-party applications, with a data processing system comprising memory and one or more processors to identify, via an interface of the data processing system, a third-party application of a plurality of third-party applications configured with application programming interfaces (“APIs”) compatible with the interface of the data processing system, transmit, to the third-party application, a query constructed based on a template that is compatible with an API of the third-party application, receive, responsive to the query, a response from the third-party application comprising an opportunity event, select a participant object that satisfies one or more parameters associated with the opportunity event, and provide, to a computing device linked with the participant object, an indication of the opportunity event.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application claims the benefit of priority under 35 U.S.C. § 119 to U.S. Provisional Patent Application Ser. No. 63/056,330, entitled “MICRO-SERVICES ARCHITECTURE TO INTEGRATE HETEROGENEOUS NODES FOR DIGITAL FEED GENERATION,” filed Jul. 24, 2020, which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

This disclosure relates generally to digital healthcare infrastructure, and more particularly to a micro-services architecture to integrate heterogeneous nodes for digital feed generation.

BACKGROUND

Individuals can obtain goods or services related to healthcare. Computing systems can provide information about such goods or services related to healthcare. However, as the number and types of goods and services increase, it can be challenging for computing systems to efficiently and reliably identify particular goods and services for an individual.

SUMMARY

Health care opportunities are increasing in complexity and scope in response to the expansion of health care services available to health care consumers. Participants in various health care support programs and health care accounts face increasingly complex and interwoven opportunities with time-sensitive conditions and complex interdependencies. However, conventional systems may not effectively integrate communication and customer service actions across heterogeneous services and accounts controlled by independent health care provider entities, resulting in a loss of opportunities due to lack of computational technological systems to rapidly and securely communicate with heterogeneous systems centered on a participant's associations with services coupled to those systems. Thus, a technological solution for a micro-services architecture to integrate heterogeneous nodes for digital feed generation is desired.

At least one aspect of this technical solution is directed to a system to present opportunities from third-party applications, with a data processing system comprising memory and one or more processors to identify, via an interface of the data processing system, a third-party application of a plurality of third-party applications configured with application programming interfaces (“APIs”) compatible with the interface of the data processing system, transmit, to the third-party application, a query constructed based on a template that is compatible with an API of the third-party application, receive, responsive to the query, a response from the third-party application comprising an opportunity event, select a participant object that satisfies one or more parameters associated with the opportunity event, and provide, to a computing device linked with the participant object, an indication of the opportunity event.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to determine to query the third-party application responsive to a trigger condition.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to crawl a web page associated with a provider of the third-party application, and determine, responsive to the crawl of the web page, to query the third-party application responsive to identifying a candidate opportunity on the web page of the provider associated with the third-party application.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to determine, based on a location of the computing device linked with the participant object, to transmit the query to the third-party application.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to train a machine learning model with historical data associated with opportunities provided by third-party applications, determine, based on information associated with the participant object input into the machine learning model, to transmit the query to the third-party application based on an output of the machine learning model.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to identify a second third-party application different from the third-party application, select a second template different than the template, the second template compatible with a second API of the second third-party application that is different than the API of the third-party application, and construct a second query for opportunities based on the second template.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to construct the query with credentials authorizing the data processing system to receive the response with the opportunity event.

At least one aspect of this technical solution is directed to a system where the credentials correspond to the participant object.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to parse the response to identify the opportunity event, construct an opportunity object to provide to the computing device based on the identified opportunity event, and transmit the opportunity object for presentation via the computing device.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to receive, responsive to transmission of the opportunity object, an indication to execute the opportunity object, and authorize, responsive to the indication, the opportunity object for execution by the participant object.

At least one aspect of this technical solution is directed to a method of presenting opportunities from third-party applications, by identifying, by a data processing system comprising one or more processors via an interface of the data processing system, a third-party application of a plurality of third-party applications configured with application programming interfaces (“APIs”) compatible with the interface of the data processing system, transmitting, by the data processing system to the third-party application, a query constructed based on a template that is compatible with an API of the third-party application, receiving, by the data processing system responsive to the query, a response from the third-party application comprising an opportunity event, selecting, by the data processing system, a participant object that satisfies one or more parameters associated with the opportunity event, and providing, by the data processing system to a computing device linked with the participant object, an indication of the opportunity event.

At least one aspect of this technical solution is directed to a method of determining, by the data processing system, to query the third-party application responsive to a trigger condition.

At least one aspect of this technical solution is directed to a method of crawling, by the data processing system, a web page associated with a provider of the third-party application, and determining, by the data processing system responsive to the crawl of the web page, to query the third-party application responsive to identifying a candidate opportunity on the web page of the provider associated with the third-party application.

At least one aspect of this technical solution is directed to a method of determining, by the data processing system based on a location of the computing device linked with the participant object, to transmit the query to the third-party application.

At least one aspect of this technical solution is directed to a method of training, by the data processing system, a machine learning model with historical data associated with opportunities provided by third-party applications, determining, by the data processing system based on information associated with the participant object input into the machine learning model, to transmit the query to the third-party application based on an output of the machine learning model.

At least one aspect of this technical solution is directed to a method of identifying, by the data processing system, a second third-party application different from the third-party application, selecting, by the data processing system, a second template different than the template, the second template compatible with a second API of the second third-party application that is different than the API of the third-party application, and constructing, by the data processing system, a second query for opportunities based on the second template.

At least one aspect of this technical solution is directed to a method of constructing, by the data processing system, the query with credentials authorizing the data processing system to receive the response with the opportunity event.

At least one aspect of this technical solution is directed to a method where the credentials correspond to the participant object.

At least one aspect of this technical solution is directed to a method of parsing, by the data processing system, the response to identify the opportunity event, constructing, by the data processing system, an opportunity object to provide to the computing device based on the identified opportunity event, and transmitting, by the data processing system, the opportunity object for presentation via the computing device.

At least one aspect of this technical solution is directed to a method of receiving, by the data processing system responsive to transmission of the opportunity object, an indication to execute the opportunity object, and authorizing, by the data processing system responsive to the indication, the opportunity object for execution by the participant object.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects and features of the present implementations will become apparent to those ordinarily skilled in the art upon review of the following description of specific implementations in conjunction with the accompanying figures, wherein:

FIG. 1A illustrates an example network environment including a client device in communication with a server device, in accordance with present implementations.

FIG. 1B illustrates an example cloud computing environment including a client device in communication with cloud service providers, in accordance with present implementations.

FIGS. 1C and 1D illustrate example computing devices in accordance with present implementations.

FIG. 2 illustrates an example cloud computing environment including an example data processing system, in accordance with present implementations.

FIG. 3 illustrates an example data processing system, in accordance with present implementations.

FIG. 4 illustrates an example participant database system further to the example data processing system of FIG. 3, in accordance with present implementations.

FIG. 5 illustrates an example opportunity database system further to the example data processing system of FIG. 3, in accordance with present implementations.

FIG. 6 illustrates an example gateway database system further to the example data processing system of FIG. 3, in accordance with present implementations.

FIG. 7 illustrates an example electronic device associated with an example data processing system, in accordance with present implementations.

FIG. 8 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, in accordance with present implementations.

FIG. 9 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, further to the method of FIG. 8, in accordance with present implementations.

FIG. 10 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, further to the method of FIG. 9, in accordance with present implementations.

FIG. 11 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, further to the method of FIG. 10, in accordance with present implementations.

DETAILED DESCRIPTION

The present implementations will now be described in detail with reference to the drawings, which are provided as illustrative examples of the implementations so as to enable those skilled in the art to practice the implementations and alternatives apparent to those skilled in the art. Notably, the figures and examples below are not meant to limit the scope of the present implementations to a single implementation, but other implementations are possible by way of interchange of some or all of the described or illustrated elements. Moreover, where certain elements of the present implementations can be partially or fully implemented using known components, only those portions of such known components that are necessary for an understanding of the present implementations will be described, and detailed descriptions of other portions of such known components will be omitted so as not to obscure the present implementations. Implementations described as being implemented in software should not be limited thereto, but can include implementations implemented in hardware, or combinations of software and hardware, and vice-versa, as will be apparent to those skilled in the art, unless otherwise specified herein. In the present specification, an implementation showing a singular component should not be considered limiting; rather, the present disclosure is intended to encompass other implementations including a plurality of the same component, and vice-versa, unless explicitly stated otherwise herein. Moreover, applicants do not intend for any term in the specification or claims to be ascribed an uncommon or special meaning unless explicitly set forth as such. Further, the present implementations encompass present and future known equivalents to the known components referred to herein by way of illustration.

A data processing system can identify opportunities at third party systems and can manage and control execution of those identified opportunities on behalf of individual participants associated with the third party systems. The data processing system can identify and respond to opportunities at various times based on opportunity events. Opportunity events can include particular times, conditions, or any combination thereof detected by the data processing system. The data processing system can detect opportunity events by, for example, crawling a web page of a third party system periodically, or receiving a system notification from a third party system responsive to a change in one or more states associated with the third party system. The data processing system can generate opportunity objects and authorize execution of those opportunity objects to effect execution of various operations at or by particular third party systems. The data processing system can generate opportunity objects based on information gathered by a crawling operation on a third party system. The data processing system can instruct a third party system to execute a particular action associated with the opportunity object to execute the opportunity. The data processing system can use credentials associated with a participant user for a third party system to crawl a secure web page associated with the participant user and to provide secure instructions associated with the participant user to authorize various opportunity executions.

The data processing system can include a micro-services architecture to integrate functionality of third-party applications to provide centralized participant account interaction and execution features. The data processing system can include an underlying system architecture including middleware or a middle tier to interface with multiple third-party applications or data sources. The underlying system architecture can have a “plug-n-play” structure. The data processing system can select a third party application, obtain a template to construct a query that is compatible with an API of a third party application, and receive a response to the query from the third party application. The data processing system can parse responses to identify attributes in responses, and process the attributes to determine opportunities. As one example, the data processing system can identify a new opportunity by selecting one or more third party applications, constructing one or more queries compatible with APIs for the third party applications, and receiving data from third party applications. As one example, an application can include a virtual medicine cabinet application.

For purposes of reading the description of the various implementations below, the following descriptions of the sections of the specification and their respective contents can be helpful:

Section A describes a network environment and computing environment which can be useful for practicing implementations described herein.

Section B describes implementations of systems and methods for a micro-services architecture to integrate heterogeneous nodes for digital feed generation.

A. Computing and Network Environment

Prior to discussing specific implementations of the present solution, it can be helpful to describe aspects of the operating environment as well as associated system components (e.g., hardware elements) in connection with the methods and systems described herein. Referring to FIG. 1A, an implementation of a network environment is depicted. In brief overview, the network environment includes one or more clients 102 a-102 n (also generally referred to as local machine(s) 102, client(s) 102, client node(s) 102, client machine(s) 102, client computer(s) 102, client device(s) 102, endpoint(s) 102, or endpoint node(s) 102) in communication with one or more servers 106 a-106 n (also generally referred to as server(s) 106, node 106, or remote machine(s) 106) via one or more networks 104. In some implementations, a client 102 has the capacity to function as both a client node seeking obtain to resources provided by a server and as a server providing obtain to hosted resources for other clients 102 a-102 n.

Although FIG. 1A shows a network 104 between the clients 102 and the servers 106, the clients 102 and the servers 106 can be on the same network 104. In some implementations, there are multiple networks 104 between the clients 102 and the servers 106. In one of these implementations, a network 104′ (not shown) can be a private network and a network 104 can be a public network. In another of these implementations, a network 104 can be a private network and a network 104′ a public network. In still another of these implementations, networks 104 and 104′ can both be private networks.

The network 104 can be connected via wired or wireless links. Wired links can include Digital Subscriber Line (DSL), coaxial cable lines, or optical fiber lines. The wireless links can include BLUETOOTH, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), an infrared channel or satellite band. The wireless links can also include any cellular network standards used to communicate among mobile devices, including standards that qualify as 1G, 2G, 3G, or 4G. The network standards can qualify as one or more generation of mobile telecommunication standards by fulfilling a specification or standards such as the specifications maintained by International Telecommunication Union. The 3G standards, for example, can correspond to the International Mobile Telecommunications-2000 (IMT-2000) specification, and the 4G standards can correspond to the International Mobile Telecommunications Advanced (IMT-Advanced) specification. Examples of cellular network standards include AMPS, GSM, GPRS, UMTS, LTE, LTE Advanced, Mobile WiMAX, and WiMAX-Advanced. Cellular network standards can use various channel access methods e.g. FDMA, TDMA, CDMA, or SDMA. In some implementations, different types of data can be transmitted via different links and standards. In other implementations, the same types of data can be transmitted via different links and standards.

The network 104 can be any type and/or form of network. The geographical scope of the network 104 can vary widely and the network 104 can be a body area network (BAN), a personal area network (PAN), a local-area network (LAN), e.g. Intranet, a metropolitan area network (MAN), a wide area network (WAN), or the Internet. The topology of the network 104 can be of any form and can include, e.g., any of the following: point-to-point, bus, star, ring, mesh, or tree. The network 104 can be an overlay network which is virtual and sits on top of one or more layers of other networks 104′. The network 104 can be of any such network topology as known to those ordinarily skilled in the art capable of supporting the operations described herein. The network 104 can utilize different techniques and layers or stacks of protocols, including, e.g., the Ethernet protocol, the internet protocol suite (TCP/IP), the ATM (Asynchronous Transfer Mode) technique, the SONET (Synchronous Optical Networking) protocol, or the SDH (Synchronous Digital Hierarchy) protocol. The TCP/IP internet protocol suite can include application layer, transport layer, internet layer (including, e.g., IPv6), or the link layer. The network 104 can be a type of a broadcast network, a telecommunications network, a data communication network, or a computer network.

In some implementations, the system can include multiple, logically-grouped servers 106. In one of these implementations, the logical group of servers can be referred to as a server farm 38 or a machine farm 38. In another of these implementations, the servers 106 can be geographically dispersed. In other implementations, a machine farm 38 can be administered as a single entity. In still other implementations, the machine farm 38 includes a plurality of machine farms 38. The servers 106 within each machine farm 38 can be heterogeneous—one or more of the servers 106 or machines 106 can operate according to one type of operating system platform (e.g., WINDOWS NT, manufactured by Microsoft Corp. of Redmond, Wash.), while one or more of the other servers 106 can operate on according to another type of operating system platform (e.g., Unix, Linux, or Mac OS X).

In one implementation, servers 106 in the machine farm 38 can be stored in high-density rack systems, along with associated storage systems, and located in an enterprise data center. In this implementation, consolidating the servers 106 in this way can improve system manageability, data security, the physical security of the system, and system performance by locating servers 106 and high performance storage systems on localized high performance networks. Centralizing the servers 106 and storage systems and coupling them with advanced system management tools allows more efficient use of server resources.

The servers 106 of each machine farm 38 do not need to be physically proximate to another server 106 in the same machine farm 38. Thus, the group of servers 106 logically grouped as a machine farm 38 can be interconnected using a wide-area network (WAN) connection or a metropolitan-area network (MAN) connection. For example, a machine farm 38 can include servers 106 physically located in different continents or different regions of a continent, country, state, city, campus, or room. Data transmission speeds between servers 106 in the machine farm 38 can be increased if the servers 106 are connected using a local-area network (LAN) connection or some form of direct connection. Additionally, a heterogeneous machine farm 38 can include one or more servers 106 operating according to a type of operating system, while one or more other servers 106 execute one or more types of hypervisors rather than operating systems. In these implementations, hypervisors can be used to emulate virtual hardware, partition physical hardware, virtualize physical hardware, and execute virtual machines that provide access to computing environments, allowing multiple operating systems to run concurrently on a host computer. Native hypervisors can run directly on the host computer. Hypervisors can include VMware ESX/ESXi, manufactured by VMWare, Inc., of Palo Alto, Calif.; the Xen hypervisor, an open source product whose development is overseen by Citrix Systems, Inc.; the HYPER-V hypervisors provided by Microsoft or others. Hosted hypervisors can run within an operating system on a second software level. Examples of hosted hypervisors can include VMware Workstation and VIRTUALBOX.

Management of the machine farm 38 can be de-centralized. For example, one or more servers 106 can comprise components, subsystems and modules to support one or more management services for the machine farm 38. In one of these implementations, one or more servers 106 provide functionality for management of dynamic data, including techniques for handling failover, data replication, and increasing the robustness of the machine farm 38. Each server 106 can communicate with a persistent store and, in some implementations, with a dynamic store.

Server 106 can be a file server, application server, web server, proxy server, appliance, network appliance, gateway, gateway server, virtualization server, deployment server, SSL VPN server, or firewall. In one implementation, the server 106 can be referred to as a remote machine or a node. In another implementation, a plurality of nodes 290 can be in the path between any two communicating servers.

Referring to FIG. 1B, a cloud computing environment is depicted. A cloud computing environment can provide client 102 with one or more resources provided by a network environment. The cloud computing environment can include one or more clients 102 a-102 n, in communication with the cloud 108 over one or more networks 104. Clients 102 can include, e.g., thick clients, thin clients, and zero clients. A thick client can provide at least some functionality even when disconnected from the cloud 108 or servers 106. A thin client or a zero client can depend on the connection to the cloud 108 or server 106 to provide functionality. A zero client can depend on the cloud 108 or other networks 104 or servers 106 to retrieve operating system data for the client device. The cloud 108 can include back end platforms, e.g., servers 106, storage, server farms or data centers.

The cloud 108 can be public, private, or hybrid. Public clouds can include public servers 106 that are maintained by third parties to the clients 102 or the owners of the clients. The servers 106 can be located off-site in remote geographical locations as disclosed above or otherwise. Public clouds can be connected to the servers 106 over a public network. Private clouds can include private servers 106 that are physically maintained by clients 102 or owners of clients. Private clouds can be connected to the servers 106 over a private network 104. Hybrid clouds 108 can include both the private and public networks 104 and servers 106.

The cloud 108 can also include a cloud based delivery, e.g. Software as a Service (SaaS) 110, Platform as a Service (PaaS) 112, and Infrastructure as a Service (IaaS) 114. IaaS can refer to a user renting the use of infrastructure resources that are needed during a specified time period. IaaS providers can offer storage, networking, servers or virtualization resources from large pools, allowing the users to quickly scale up by accessing more resources as needed. Examples of IaaS can include infrastructure and services (e.g., EG-32) provided by OVH HOSTING of Montreal, Quebec, Canada, AMAZON WEB SERVICES provided by Amazon.com, Inc., of Seattle, Wash., RACKSPACE CLOUD provided by Rackspace US, Inc., of San Antonio, Tex., Google Compute Engine provided by Google Inc. of Mountain View, Calif., or RIGHTSCALE provided by RightScale, Inc., of Santa Barbara, Calif. PaaS providers can offer functionality provided by IaaS, including, e.g., storage, networking, servers or virtualization, as well as additional resources such as, e.g., the operating system, middleware, or runtime resources. Examples of PaaS include WINDOWS AZURE provided by Microsoft Corporation of Redmond, Wash., Google App Engine provided by Google Inc., and HEROKU provided by Heroku, Inc. of San Francisco, Calif. SaaS providers can offer the resources that PaaS provides, including storage, networking, servers, virtualization, operating system, middleware, or runtime resources. In some implementations, SaaS providers can offer additional resources including, e.g., data and application resources. Examples of SaaS include GOOGLE APPS provided by Google Inc., SALESFORCE provided by Salesforce.com Inc. of San Francisco, Calif., or OFFICE 365 provided by Microsoft Corporation. Examples of SaaS can also include data storage providers, e.g. DROPBOX provided by Dropbox, Inc. of San Francisco, Calif., Microsoft SKYDRIVE provided by Microsoft Corporation, Google Drive provided by Google Inc., or Apple ICLOUD provided by Apple Inc. of Cupertino, Calif.

Clients 102 can access IaaS resources with one or more IaaS standards, including, e.g., Amazon Elastic Compute Cloud (EC2), Open Cloud Computing Interface (OCCI), Cloud Infrastructure Management Interface (CIMI), or OpenStack standards. Some IaaS standards can allow clients access to resources over HTTP, and can use Representational State Transfer (REST) protocol or Simple Object Access Protocol (SOAP). Clients 102 can access PaaS resources with different PaaS interfaces. Some PaaS interfaces use HTTP packages, standard Java APIs, JavaMail API, Java Data Objects (JDO), Java Persistence API (JPA), Python APIs, web integration APIs for different programming languages including, e.g., Rack for Ruby, WSGI for Python, or PSGI for Perl, or other APIs that can be built on REST, HTTP, XML, or other protocols. Clients 102 can access SaaS resources through the use of web-based user interfaces, provided by a web browser (e.g. GOOGLE CHROME, Microsoft INTERNET EXPLORER, or Mozilla Firefox provided by Mozilla Foundation of Mountain View, Calif.). Clients 102 can also access SaaS resources through smartphone or tablet applications, including, e.g., Salesforce Sales Cloud, or Google Drive app. Clients 102 can also access SaaS resources through the client operating system, including, e.g., Windows file system for DROPBOX.

In some implementations, access to IaaS, PaaS, or SaaS resources can be authenticated. For example, a server or authentication server can authenticate a user via security certificates, HTTPS, or API keys. API keys can include various encryption standards such as, e.g., Advanced Encryption Standard (AES). Data resources can be sent over Transport Layer Security (TLS) or Secure Sockets Layer (SSL).

The client 102 and server 106 can be deployed as and/or executed on any type and form of computing device, e.g. a computer, network device or appliance capable of communicating on any type and form of network and performing the operations described herein. FIGS. 1C and 1D depict block diagrams of a computing device 100 useful for practicing an implementation of the client 102 or a server 106. As shown in FIGS. 1C and 1D, each computing device 100 includes a central processing unit 121, and a main memory unit 122. As shown in FIG. 1C, a computing device 100 can include a storage device 128, an installation device 116, a network interface 118, an I/O controller 123, display devices 124 a-124 n, a keyboard 126 and a pointing device 127, e.g. a mouse. The storage device 128 can include, without limitation, an operating system, software, and a software of data processing system (DPS) 120. As shown in FIG. 1D, each computing device 100 can also include additional optional elements, e.g. a memory port 103, a bridge 170, one or more input/output devices 130 a-130 n (generally referred to using reference numeral 130), and a cache memory 140 in communication with the central processing unit 121.

The central processing unit 121 is any logic circuitry that responds to and processes instructions fetched from the main memory unit 122. In many implementations, the central processing unit 121 is provided by a microprocessor unit, e.g.: those manufactured by Intel Corporation of Mountain View, Calif.; those manufactured by Motorola Corporation of Schaumburg, Ill.; the ARM processor and TEGRA system on a chip (SoC) manufactured by Nvidia of Santa Clara, Calif.; the POWER7 processor, those manufactured by International Business Machines of White Plains, N.Y.; or those manufactured by Advanced Micro Devices of Sunnyvale, Calif. The computing device 100 can be based on any of these processors, or any other processor capable of operating as described herein. The central processing unit 121 can utilize instruction level parallelism, thread level parallelism, different levels of cache, and multi-core processors. A multi-core processor can include two or more processing units on a single computing component. Examples of multi-core processors include the AMD PHENOM IIX2, INTEL CORE i5 and INTEL CORE i7.

Main memory unit 122 can include one or more memory chips capable of storing data and allowing any storage location to be directly accessed by the microprocessor 121. Main memory unit 122 can be volatile and faster than storage 128 memory. Main memory units 122 can be Dynamic random access memory (DRAM) or any variants, including static random access memory (SRAM), Burst SRAM or SynchBurst SRAM (B SRAM), Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended Data Output DRAM (BEDO DRAM), Single Data Rate Synchronous DRAM (SDR SDRAM), Double Data Rate SDRAM (DDR SDRAM), Direct Rambus DRAM (DRDRAM), or Extreme Data Rate DRAM (XDR DRAM). In some implementations, the main memory 122 or the storage 128 can be non-volatile; e.g., non-volatile read access memory (NVRAM), flash memory non-volatile static RAM (nvSRAM), Ferroelectric RAM (FeRAM), Magnetoresistive RAM (MRAM), Phase-change memory (PRAM), conductive-bridging RAM (CBRAM), Silicon-Oxide-Nitride-Oxide-Silicon (SONOS), Resistive RAM (RRAM), Racetrack, Nano-RAM (NRAM), or Millipede memory. The main memory 122 can be based on any of the above described memory chips, or any other available memory chips capable of operating as described herein. In the implementation shown in FIG. 1C, the processor 121 communicates with main memory 122 via a system bus 150 (described in more detail below). FIG. 1D depicts an implementation of a computing device 100 in which the processor communicates directly with main memory 122 via a memory port 103. For example, in FIG. 1D the main memory 122 can be DRDRAM.

FIG. 1D depicts an implementation in which the main processor 121 communicates directly with cache memory 140 via a secondary bus, sometimes referred to as a backside bus. In other implementations, the main processor 121 communicates with cache memory 140 using the system bus 150. Cache memory 140 typically has a faster response time than main memory 122 and is typically provided by SRAM, BSRAM, or EDRAM. In the implementation shown in FIG. 1D, the processor 121 communicates with various I/O devices 130 via a local system bus 150. Various buses can be used to connect the central processing unit 121 to any of the I/O devices 130, including a PCI bus, a PCI-X bus, or a PCI-Express bus, or a NuBus. For implementations in which the I/O device is a video display 124, the processor 121 can use an Advanced Graphics Port (AGP) to communicate with the display 124 or the I/O controller 123 for the display 124. FIG. 1D depicts an implementation of a computer 100 in which the main processor 121 communicates directly with I/O device 130 b or other processors 121′ via HYPERTRANSPORT, RAPIDIO, or INFINIBAND communications technology. FIG. 1D also depicts an implementation in which local busses and direct communication are mixed: the processor 121 communicates with I/O device 130 a using a local interconnect bus while communicating with I/O device 130 b directly.

A wide variety of I/O devices 130 a-130 n can be present in the computing device 100. Input devices can include keyboards, mice, trackpads, trackballs, touchpads, touch mice, multi-touch touchpads and touch mice, microphones, multi-array microphones, drawing tablets, cameras, single-lens reflex camera (SLR), digital SLR (DSLR), CMOS sensors, accelerometers, infrared optical sensors, pressure sensors, magnetometer sensors, angular rate sensors, depth sensors, proximity sensors, ambient light sensors, gyroscopic sensors, or other sensors. Output devices can include video displays, graphical displays, speakers, headphones, inkjet printers, laser printers, and 3D printers.

Devices 130 a-130 n can include a combination of multiple input or output devices, including, e.g., Microsoft KINECT, Nintendo Wiimote for the WII, Nintendo WII U GAMEPAD, or Apple IPHONE. Some devices 130 a-130 n allow gesture recognition inputs through combining some of the inputs and outputs. Some devices 130 a-130 n provides for facial recognition which can be utilized as an input for different purposes including authentication and other commands. Some devices 130 a-130 n provides for voice recognition and inputs, including, e.g., Microsoft KINECT, SIRI for IPHONE by Apple, Google Now or Google Voice Search.

Additional devices 130 a-130 n have both input and output capabilities, including, e.g., haptic feedback devices, touchscreen displays, or multi-touch displays. Touchscreen, multi-touch displays, touchpads, touch mice, or other touch sensing devices can use different technologies to sense touch, including, e.g., capacitive, surface capacitive, projected capacitive touch (PCT), in-cell capacitive, resistive, infrared, waveguide, dispersive signal touch (DST), in-cell optical, surface acoustic wave (SAW), bending wave touch (BWT), or force-based sensing technologies. Some multi-touch devices can allow two or more contact points with the surface, allowing advanced functionality including, e.g., pinch, spread, rotate, scroll, or other gestures. Some touchscreen devices, including, e.g., Microsoft PIXELSENSE or Multi-Touch Collaboration Wall, can have larger surfaces, such as on a table-top or on a wall, and can also interact with other electronic devices. Some I/O devices 130 a-130 n, display devices 124 a-124 n or group of devices can be augment reality devices. The I/O devices can be controlled by an I/O controller 123 as shown in FIG. 1C. The I/O controller can control one or more I/O devices, such as, e.g., a keyboard 126 and a pointing device 127, e.g., a mouse or optical pen. Furthermore, an I/O device can also provide storage and/or an installation medium 116 for the computing device 100. In still other implementations, the computing device 100 can provide USB connections (not shown) to receive handheld USB storage devices. In further implementations, an I/O device 130 can be a bridge between the system bus 150 and an external communication bus, e.g. a USB bus, a SCSI bus, a FireWire bus, an Ethernet bus, a Gigabit Ethernet bus, a Fibre Channel bus, or a Thunderbolt bus.

In some implementations, display devices 124 a-124 n can be connected to I/O controller 123. Display devices can include, e.g., liquid crystal displays (LCD), thin film transistor LCD (TFT-LCD), blue phase LCD, electronic papers (e-ink) displays, flexile displays, light emitting diode displays (LED), digital light processing (DLP) displays, liquid crystal on silicon (LCOS) displays, organic light-emitting diode (OLED) displays, active-matrix organic light-emitting diode (AMOLED) displays, liquid crystal laser displays, time-multiplexed optical shutter (TMOS) displays, or 3D displays. Examples of 3D displays can use, e.g. stereoscopy, polarization filters, active shutters, or autostereoscopy. Display devices 124 a-124 n can also be a head-mounted display (HMD). In some implementations, display devices 124 a-124 n or the corresponding I/O controllers 123 can be controlled through or have hardware support for OPENGL or DIRECTX API or other graphics libraries.

In some implementations, the computing device 100 can include or connect to multiple display devices 124 a-124 n, which each can be of the same or different type and/or form. As such, any of the I/O devices 130 a-130 n and/or the I/O controller 123 can include any type and/or form of suitable hardware, software, or combination of hardware and software to support, enable or provide for the connection and use of multiple display devices 124 a-124 n by the computing device 100. For example, the computing device 100 can include any type and/or form of video adapter, video card, driver, and/or library to interface, communicate, connect or otherwise use the display devices 124 a-124 n. In one implementation, a video adapter can include multiple connectors to interface to multiple display devices 124 a-124 n. In other implementations, the computing device 100 can include multiple video adapters, with each video adapter connected to one or more of the display devices 124 a-124 n. In some implementations, any portion of the operating system of the computing device 100 can be configured for using multiple displays 124 a-124 n. In other implementations, one or more of the display devices 124 a-124 n can be provided by one or more other computing devices 100 a or 100 b connected to the computing device 100, via the network 104. In some implementations software can be designed and constructed to use another computer's display device as a second display device 124 a for the computing device 100. For example, in one implementation, an Apple iPad can connect to a computing device 100 and use the display of the device 100 as an additional display screen that can be used as an extended desktop. One ordinarily skilled in the art will recognize and appreciate the various ways and implementations that a computing device 100 can be configured to have multiple display devices 124 a-124 n.

Referring again to FIG. 1C, the computing device 100 can comprise a storage device 128 (e.g. one or more hard disk drives or redundant arrays of independent disks) for storing an operating system or other related software, and for storing application software programs such as any program related to the software 120 for the centralized state processing system. Examples of storage device 128 include, e.g., hard disk drive (HDD); optical drive including CD drive, DVD drive, or BLU-RAY drive; solid-state drive (SSD); USB flash drive; or any other device suitable for storing data. Some storage devices can include multiple volatile and non-volatile memories, including, e.g., solid state hybrid drives that combine hard disks with solid state cache. Some storage device 128 can be non-volatile, mutable, or read-only. Some storage device 128 can be internal and connect to the computing device 100 via a bus 150. Some storage device 128 can be external and connect to the computing device 100 via a I/O device 130 that provides an external bus. Some storage device 128 can connect to the computing device 100 via the network interface 118 over a network 104, including, e.g., the Remote Disk for MACBOOK AIR by Apple. Some client devices 100 may not require a non-volatile storage device 128 and can be thin clients or zero clients 102. Some storage device 128 can also be used as an installation device 116, and can be suitable for installing software and programs. Additionally, the operating system and the software can be run from a bootable medium, for example, a bootable CD, e.g. KNOPPIX, a bootable CD for GNU/Linux that is available as a GNU/Linux distribution from knoppix.net.

Client device 100 can also install software or application from an application distribution platform. Examples of application distribution platforms include the App Store for iOS provided by Apple, Inc., the Mac App Store provided by Apple, Inc., GOOGLE PLAY for Android OS provided by Google Inc., Chrome Webstore for CHROME OS provided by Google Inc., and Amazon Appstore for Android OS and KINDLE FIRE provided by Amazon.com, Inc. An application distribution platform can facilitate installation of software on a client device 102. An application distribution platform can include a repository of applications on a server 106 or a cloud 108, which the clients 102 a-102 n can access over a network 104. An application distribution platform can include application developed and provided by various developers. A user of a client device 102 can select, purchase and/or download an application via the application distribution platform.

Furthermore, the computing device 100 can include a network interface 118 to interface to the network 104 through a variety of connections including, but not limited to, standard telephone lines LAN or WAN links (e.g., 802.11, T1, T3, Gigabit Ethernet, Infiniband), broadband connections (e.g., ISDN, Frame Relay, ATM, Gigabit Ethernet, Ethernet-over-SONET, ADSL, VDSL, BPON, GPON, fiber optical including FiOS), wireless connections, or some combination of any or all of the above. Connections can be established using a variety of communication protocols (e.g., TCP/IP, Ethernet, ARCNET, SONET, SDH, Fiber Distributed Data Interface (FDDI), IEEE 802.11a/b/g/n/ac CDMA, GSM, WiMax and direct asynchronous connections). In one implementation, the computing device 100 communicates with other computing devices 100′ via any type and/or form of gateway or tunneling protocol e.g. Secure Socket Layer (SSL) or Transport Layer Security (TLS), or the Citrix Gateway Protocol manufactured by Citrix Systems, Inc. of Ft. Lauderdale, Fla. The network interface 118 can comprise a built-in network adapter, network interface card, PCMCIA network card, EXPRESSCARD network card, card bus network adapter, wireless network adapter, USB network adapter, modem or any other device suitable for interfacing the computing device 100 to any type of network capable of communication and performing the operations described herein.

A computing device 100 of the sort depicted in FIGS. 1B and 1C can operate under the control of an operating system, which controls scheduling of tasks and access to system resources. The computing device 100 can be running any operating system such as any of the versions of the MICROSOFT WINDOWS operating systems, the different releases of the Unix and Linux operating systems, any version of the MAC OS for Macintosh computers, any embedded operating system, any real-time operating system, any open source operating system, any proprietary operating system, any operating systems for mobile computing devices, or any other operating system capable of running on the computing device and performing the operations described herein. Typical operating systems include, but are not limited to: WINDOWS 2000, WINDOWS Server 2012, WINDOWS CE, WINDOWS Phone, WINDOWS XP, WINDOWS VISTA, and WINDOWS 7, WINDOWS RT, and WINDOWS 8 all of which are manufactured by Microsoft Corporation of Redmond, Wash.; MAC OS and iOS, manufactured by Apple, Inc. of Cupertino, Calif.; and Linux, a freely-available operating system, e.g. Linux Mint distribution (“distro”) or Ubuntu, distributed by Canonical Ltd. of London, United Kingdom; or Unix or other Unix-like derivative operating systems; and Android, designed by Google, of Mountain View, Calif., among others. Some operating systems, including, e.g., the CHROME OS by Google, can be used on zero clients or thin clients, including, e.g., CHROMEBOOKS.

The computer system 100 can be any workstation, telephone, desktop computer, laptop or notebook computer, netbook, ULTRABOOK, tablet, server, handheld computer, mobile telephone, smartphone or other portable telecommunications device, media playing device, a gaming system, mobile computing device, or any other type and/or form of computing, telecommunications or media device that is capable of communication. The computer system 100 has sufficient processor power and memory capacity to perform the operations described herein. In some implementations, the computing device 100 can have different processors, operating systems, and input devices consistent with the device. The Samsung GALAXY smartphones, e.g., operate under the control of Android operating system developed by Google, Inc. GALAXY smartphones receive input via a touch interface.

In some implementations, the computing device 100 is a gaming system. For example, the computer system 100 can comprise a PLAYSTATION 3, or PERSONAL PLAYSTATION PORTABLE (PSP), or a PLAYSTATION VITA device manufactured by the Sony Corporation of Tokyo, Japan, a NINTENDO DS, NINTENDO 3DS, NINTENDO WII, or a NINTENDO WII U device manufactured by Nintendo Co., Ltd., of Kyoto, Japan, an XBOX 360 device manufactured by the Microsoft Corporation of Redmond, Wash.

In some implementations, the computing device 100 is a digital audio player such as the Apple IPOD, IPOD Touch, and IPOD NANO lines of devices, manufactured by Apple Computer of Cupertino, Calif. Some digital audio players can have other functionality, including, e.g., a gaming system or any functionality made available by an application from a digital application distribution platform. For example, the IPOD Touch can access the Apple App Store. In some implementations, the computing device 100 is a portable media player or digital audio player supporting file formats including, but not limited to, MP3, WAV, M4A/AAC, WMA Protected AAC, AIFF, Audible audiobook, Apple Lossless audio file formats and .mov, .m4v, and .mp4 MPEG-4 (H.264/MPEG-4 AVC) video file formats.

In some implementations, the computing device 100 is a tablet e.g. the IPAD line of devices by Apple; GALAXY TAB family of devices by Samsung; or KINDLE FIRE, by Amazon.com, Inc. of Seattle, Wash. In other implementations, the computing device 100 is an eBook reader, e.g. the KINDLE family of devices by Amazon.com, or NOOK family of devices by Barnes & Noble, Inc. of New York City, N.Y.

In some implementations, the communications device 102 includes a combination of devices, e.g. a smartphone combined with a digital audio player or portable media player. For example, one of these implementations is a smartphone, e.g. the IPHONE family of smartphones manufactured by Apple, Inc.; a Samsung GALAXY family of smartphones manufactured by Samsung, Inc.; or a Motorola DROID family of smartphones. In yet another implementation, the communications device 102 is a laptop or desktop computer equipped with a web browser and a microphone and speaker system, e.g. a telephony headset. In these implementations, the communications devices 102 are web-enabled and can receive and initiate phone calls. In some implementations, a laptop or desktop computer is also equipped with a webcam or other video capture device that enables video chat and video call.

In some implementations, the status of one or more machines 102, 106 in the network 104 are monitored, generally as part of network management. In one of these implementations, the status of a machine can include an identification of load information (e.g., the number of processes on the machine, CPU and memory utilization), of port information (e.g., the number of available communication ports and the port addresses), or of session status (e.g., the duration and type of processes, and whether a process is active or idle). In another of these implementations, this information can be identified by a plurality of metrics, and the plurality of metrics can be applied at least in part towards decisions in load distribution, network traffic management, and network failure recovery as well as any aspects of operations of the present solution described herein. Aspects of the operating environments and components described above will become apparent in the context of the systems and methods disclosed herein.

B. Generation of a Real-Time Trigger Based Digital Feed

Systems and methods in accordance with present implementations can generate opportunities for consuming healthcare products and services based on detecting various promotions, prices, accounts, or product offerings by a number of healthcare support services. Present implementations can detect state or change in of particular promotions, prices, accounts, or product offerings linked to a healthcare participant and present opportunities for interacting with those promotions, prices, accounts, or product offerings, allowing a user to select one or more of those opportunities and, in response, to modify a healthcare service or modify a pattern of product consumption individualized to that user. Present implementations can thus include a microservices engine to coordinate and control interaction with third party system, an opportunity engine 340 to generate and control opportunity objects associated with third party systems, a security engine 350 to permit and restrict communication with third party systems and participant systems, and a system scheduler 360 to synchronize and manage operations of the data processing system.

Referring now to FIG. 2, a block diagram depicting an implementation of a system 200 comprising a centralized state processing system is shown. In brief overview, the system 200 can include a data processing system 120 (“DPS”) that can receive and/or transmit data via a network 104 with participant computing devices 232 a-n, third-party administrator devices 240 a-n, employer devices 238 a-n, point-of-sale terminals 236 a-n, or heterogeneous electronic funding sources 234 a-n. The DPS 120 can include a communications interface 204 that is configured with one or more communications ports, application programming interfaces, network protocols (e.g., TCP/IP), authentication protocols, or security protocols (e.g., SSL). The DPS 120 can include, interface with, or otherwise access a gateway engine 310 that controls communication between the DPS 120 and heterogeneous nodes including but not limited to the participant computing devices 232 a-n, third-party administrator devices 240 a-n, employer devices 238 a-n, point-of-sale terminals 236 a-n, and heterogeneous electronic funding sources 234 a-n. The DPS 120 can include, interface with, or otherwise access a microservices engine 320 that controls communications within the DPS 120 and between components thereof in accordance with one or more microservice communication criteria, objects, protocols, or any combination thereof, for example. The DPS 120 can include, interface with, or otherwise access an opportunity engine 340 that analyzes, transmits, executes, or any combination thereof, for example, opportunity objects. The DPS 120 can include, interface with, or otherwise access a security engine 350 that controls one or more security, encryption, authentication, authorization, credentialing, or like operations, including but not limited to one or more policies, rules, restrictions, challenges, or any combination thereof, for example. The DPS 120 can include, interface with, or otherwise access a system scheduler 360 that controls asynchronous, processing, batch processing, or any combination thereof, for example associated with at least one of the DPS 120 and the microservices engine 320. The DPS 120 can include one or more databases or data structures that store information to facilitate the systems and methods of the present solution, such as database 330. The database 330 can include data structures, files or otherwise categorize information into different databases based at least partially by object. The database 330 can also include one or more policies, profiles, merchant information, or historical transaction activity, or any combination thereof, for example.

The system 120, gateway engine 310, microservices engine 320, opportunity engine 340, security engine 350, and system scheduler 360 can each include one or more processing units or other logic devices such as programmable logic array engines, modules, or circuitry designed and constructed to facilitate managing security on a network infrastructure. The DPS 120 can include the components 100 shown in FIG. 1C or FIG. 1D, or be configured to operate as a service in cloud 108. The DPS 120 can include or interact with one or more servers 106 a-n and clients 102 a-n. The participant computing devices 232 a-n, POS terminals 236 a-n, employer devices 238 a-n, TPA devices 240 a-n, or heterogeneous electronic funding sources 234 a-n can each include one or more component or functionality of client computing devices 102 a-n or server 106 a-n.

In some implementations, the DPS 120 can employ a multitier architecture such as a client-server architecture in which presentation, application processing, and data management functions are logically or physically separated. The presentation tier, or front-end, can include the communications interface 204 that can serve static content or dynamic content to be rendered by the client 102 (e.g., by a web browser executing on client 102). The presentation tier or web server can interact or communicate with the application tier to obtain data to provide to the client 102, computing devices, 232 a-n, TPA devices 240 a-n, employer devices 238 a-n, funding sources 234 a-n, or POS terminals 120 a-n. The application tier can include the event control engine 310 and the opportunity engine 320. The application tier can interact with the data tier to obtain the transaction data. The data tier can include data persistence mechanisms (database servers, file shares, etc.) and the data access layer that encapsulates the persistence mechanisms and exposes the data. The data tier can include databases 214. The data tier can include an application programming interface (API) to the application tier. The databases 214 can include stored procedures (e.g., SQL statements) that perform tasks with respect the stored data.

The system 200 can include, access, or otherwise communicate with one or more third-party administrator (“TPA”) devices 240 a-n. A TPA can refer to an organization that processes insurance claims or certain aspects of employee benefit plans for a separate entity. A TPA can refer to organizations within the insurance industry which “administer” other services such as Underwriting or Customer Service. In some cases, a TPA can handle the claims processing for employers 238 a-n that self-insures its employees 232 a-n. Thus, the employers 238 a-n are acting as an insurance company and underwrites the risk. The risk of loss can remains with the employer 238 a-n, and not with the TPA 240 a-n. An insurance company may also use a TPA 240 a-n to manage its claims processing, provider networks, utilization review, or membership functions. The TPA 240 a-n can handle many aspects of other employee benefit plans such as the processing of retirement plans and flexible spending accounts. Many employee benefit plans have highly technical aspects and difficult administration that can make using a specialized entity such as a TPA 240 a-n more cost effective than doing the same processing in house.

In the health care industry, for example, TPAs 240 a-n can administer all or a portion of the claims process. TPAs 240 a-n can be contracted by a health insurer or self-insuring companies to administer services, including claims administration, premium collection, enrollment and other administrative activities. For example, an employer 238 a-n may choose to help finance the health care costs of its employees 232 a-n by contracting with a TPA 240 a-n to administer many aspects of a self-funded health care plan.

Administrators, such as companies or health insurance providers, can establish electronic benefits accounts such as flexible spending accounts or healthcare tax benefit accounts (e.g., health savings accounts) for participants such as employees, subscribers, or customers. These electronic benefits accounts can provide a tax advantage for the participants. Administrators that establish or provide electronic tax benefits accounts for various participants of those accounts can utilize backend information technology infrastructure to process, analyze, monitor or manage the electronic tax benefits accounts. The tax benefit management information technology infrastructure can be configured with processing rules that are applied to electronic transactions. Electronic transactions can include allocating funds to the tax benefit account, withdrawing funds from the tax benefit account, making a purchase with funds from the tax benefit account, modifying a profile of the tax benefit account, or submitting a claim. The management information technology infrastructure can apply one or more rules to each type of transaction to determine an event. As the types of transactions and rules increase in number and complexity, the types and events can also increase in number and complexity, thereby consuming an increasing amount of resources of the information technology infrastructure. For example, events such as a card denial increases the number of transaction attempts, communications with the server, account resets, profile corruption, or resources consumed by a point-of-sale device initiating the transaction.

The employer devices 238 a-n can refer to a device used by an entity or organization that is associated with the participant computing devices 232 a-n of the employees of the employer. For example, Employer A can be a software company that has a thousand employees associated with the participant computing devices 232 a-n. The employees can obtain health care or other services, and pay for those services at a POS terminal 236 a-n of the service provider.

Data packets can be generated by a device 240 a-n at an administrator. The device can refer to an administrator device (“administrator device”) such as administrator device 240 a-n. The administrator device 240 a-n may monitor data from the various electronic benefits accounts associated with the administrator. The accounts associated with the administrator may be accounts that are managed or maintained by the administrator. The administrator may be a point of contact for customers or participants of the associated accounts. In some implementations, the client 102, which may correspond to an individual participant of the administrator's electronic benefits account, may access the account and perform a number of actions with respect to the account, such as, fund the account (e.g., via heterogeneous electronic funding sources 234 a-n), withdraw from the account, charge the account, or any combination thereof, for example. The administrator of the electronic benefits account, as the caretaker of the account, may adjust parameters associated with the account, such as, monthly fees, minimum running balances, etc. At the same time, the DPS 120 may monitor the data, parameters, and performance of the account and store the information under an administrator profile associated with the administrator of the account. The DPS 120 may receive the data associated with the individual participants and their individual accounts from the client's 102 and the parameter data associated with the accounts from the administrator device 240 a-n via the network 104.

An administrator device 240 a-n can be the place where an administrator may perform various functions of the administrator, for example, functions associated with electronic benefits accounts of the administrator. The administrator device 240 a-n is the point at an administrator that may send requests or transaction information to the DPS 120 for further processing or data collection. The administrator device 240 a-n may also be configured to transmit an identifier associated with the administrator corresponding to the administrator device 240 a-n for identification by the DPS 120. In some implementations, the receiving of the identifier initiates a fraud detection and control process.

The administrator device 240 a-n can include hardware and software. Administrators can utilize scanners, EFTPOS terminals, touch screens and any other wide variety of hardware and software available for use with administrator device 240 a-n. For example, an administrator can use software to make adjustments to parameters associated with their electronic benefits accounts.

The administrator device 240 a-n can include advanced features to cater to different functionality, such as account participant forecasts and estimates, account simulation, communication with participants of accounts, performing actions associated with individual participant accounts (e.g., freezing an account), collecting data from one or more of the participant accounts, etc., all built into the administrator software. The administrator device 240 a-n can be configured to execute user-input commands with respect to the electronic benefits accounts of the administrator.

In some implementations, the communication interface 204 can receive data packets. The data packets can carry one or more electronic transactions. In some cases, the data packets can carry multiple electronic transactions. In some cases, the data packets can be received over a duration of time. The electronic transactions can occur over the duration of time. In some cases, the electronic transaction information carried via the data packets can be received by the DPS 120 in real-time, such as responsive to the occurrence of the electronic transaction. Real-time or near-real-time communication can include, but is not limited to, reducing or eliminating latency of or delay in communication to below a perceivable level by a user. As one example, latency or delay can be introduced by incompatibilities between third-party computing systems, or databases, and can be reduced or eliminated by interconnection of those systems or databases through automated communication interfaces compatible with both. In some cases, the DPS 120 can receive the information about the electronic transactions in a bulk upload or batch upload. Receiving the information about the electronic transaction sin a bulk upload or batch upload can reduce computing resource utilization or network bandwidth usage, thereby improving the efficiency of the DPS 120. For example, the provider of the information about the electronic transactions can compress the information and generate data packets carrying the compressed information in a single batch or bulk transmission, thereby reducing network bandwidth utilization.

The electronic transaction information carried via the data packets can include information that facilitates performance of the electronic transaction, or analyzing the electronic transaction to detect fraudulent activity. The electronic transaction can a source identifier pointing to a data structure storing a resource, a destination identifier corresponding to a data structure to transfer the resource, and an intermediary identifier corresponding to an entity that provides at least a portion of the resource stored in the data structure. The source identifier can refer to an account identifier that contains the resource being transferred from a source to a destination. The source identifier can refer to an account of an employee of an employer. The source identifier can correspond to an account associated with a participant computing device 232. The resource can correspond to an electronic resource or physical resource being represented in an electronic form. The resource can refer to or include a token, currency, points, or other resource that can be transferred from the source to a destination. The destination identifier an correspond to an entity or organization receiving the resource. The destination identifier can correspond to a provider of a service or good that is receiving the resource in return for performing the service or providing the good to the employee. The intermediary identifier can correspond to an entity that stores, holds, manages, provides, or maintains the resource. The intermediary identifier can refer to or correspond to the employer device 238 a-n, a heterogeneous electronic funding source 234 a-n or TPA 240 a-n.

An identifier corresponding to a data structure can refer to or include an identifier pointing to a data structure, such as a memory pointer. The identifier corresponding to a data structure can refer to or include an identifier used by a lookup to retrieve, identify, access or select the data structure. The identifier can label the data structure. The identifier can be mapped to the data structure.

The data packets or electronic transaction can be generated by a device at a merchant to conduct an electronic transaction at the merchant. The device can refer to a point of sale terminal (“POS terminal”) such as POS terminal 236 a-n. In some implementations, the POS terminals 236 a-n are the devices at which retail transactions are initiated. The POS terminals 236 a-n are the points at which a customer of the entity or merchant makes a payment to the merchant in exchange for goods or services. At the point of sale the merchant can calculate the amount owed by the customer and provide options for the customer to make payment. The merchant can also issue a receipt for the transaction.

The POS terminal 236 a-n can include hardware and software. Merchants can utilize weighing scales, scanners, electronic and manual cash registers, EFTPOS terminals, touch screens and any other wide variety of hardware and software available for use with POS terminal 236 a-n. For example, a pharmacy can use software to customize the item or service sold when a customer has a special medication request.

The POS terminal 236 a-n can include advanced features to cater to different functionality, such as inventory management, CRM, financials, warehousing, flexible spending account transactions, etc., all built into the POS software. The POS terminal 236 a-n can be configured to conduct a transactions using a debit card, multipurse card, Bluetooth, near field communications, smartphone, smartwatch, mobile telecommunications computing device, wearable communications, RFID, etc.

The DPS 120 can include a communications interface 204. The communications interface 204 can execute on one or more processors of a server. The communications interface 204 can include one or more communications ports and be configured with one or more network protocols. Communications ports can include, e.g., network ports, Ethernet ports, WAN ports, I/O ports, or software ports. The communication port can be configured with a network protocol such as Transport Layer Protocols such as TCP/IP or UDP that are configured to receive and process data packets received via a computer network. The port can include or be associated with an IP address of a host and a protocol type of the communication.

The communications interface 204 can receive data packets generated by the POS terminal 236 a-n responsive to an electronic transaction resulting in transmission of a request to adjudicate a single claim against an electronic benefits account. In some implementations, the request to adjudicate a single claim against the electronic benefits account is transmitted responsive to a user swiping a payment card at the POS terminal. The payment card can include identifying information that can be used to identify an account identifier of the electronic benefit account (e.g., source identifier) against which to adjudicate the claim. The data packets can include header information and payload information. Multiple data packets can be strung together in a sequence. The header information can refer to TCP/IP headers that include fields such as source port, destination port, sequence number, acknowledge number, window size, etc. The payload information of the data packet can include information related to the electronic transaction, the request to adjudicate a single claim, the merchant, or the customer. The DPS 120 can receive the data packet with header information and payload information and process the packets to obtain information for further processing. The payload can include data identifying the POS terminal 236 a-n (e.g., POS terminal 236 a) at which the electronic transaction occurred, the merchant providing the POS terminal 236 a, a merchant category of the merchant, financial information associated with the user performing the electronic transaction (e.g., via a card swipe or other communication technique used to perform the electronic transaction), an amount of expenditures of the electronic transaction, and other information facilitating adjudication of the single claim. The data packets (e.g., via the payload) can include the request to adjudicate the single claim. The request can specify the electronic benefits account for adjudication. The request can specify information for identifying a policy for performing the adjudication. The payload can include data identifying a merchant category of the merchant, an electronic benefits account, and a monetary amount of the electronic transaction.

The data packets can carry data identifying a merchant or merchant category of the merchant. In some implementations, the data carried by the data packets include a merchant category code or identifier (e.g., dental, medical, etc.). In some implementations, the data identifies a merchant, and the DPS 120 determines a merchant category based on the identification of the merchant by, for example, using a merchant to merchant category mapping or lookup table stored in database. In some implementations, the data packets carrying the request to adjudicate the single claim against the electronic benefits account include a data structure having a first field indicating a merchant identifier, a second field indicating a total amount of expenditures, and a third field indicating the electronics benefit account. In some implementations, the data packets are generated by a merchant device (e.g., a client device 102 of a merchant) to conduct an electronic transaction at the merchant, and the data packets carry data identifying a merchant category of the merchant, the electronic benefits account maintained and configured on the DPS 120, and a total monetary amount of the electronic transaction.

The data packets (e.g., payload of the data packets) can further identify an electronic account maintained and configured on the server. The electronic account can be maintained and configured in a database 214. The electronic account can correspond to a user and have a unique identifier. The unique identifier can include numbers, letters, characters, symbols, etc. The electronic account can be associated with the customer making the transaction at the merchant. The POS terminal 236 a can receive or determine the electronic account identifier via a card swipe or other communication technique employed at the POS terminal 236 a, which the POS 236 a can then convey to the DPS 120.

The communications interface 120 can further receive data packets (e.g., payload information) identifying a monetary amount of the electronic transaction, such as a total amount of expenditures. The monetary amount can be for the purchase of goods or services made at the merchant. The monetary amount of the transaction can refer to the amount of funds in consideration for goods or services obtained from the entity or merchant. The merchant or entity can refer to the entity at which a point-of-sale terminal or device used to make the transaction is located or with which the terminal is associated. The monetary amount can be in any currency (e.g., United States dollars) or units. The monetary amount can be further tied to a category, such as medical services.

In some implementations, the POS terminal 236 a can generate multiple data packets for a single transaction. The multiple data packets can each include a header and a payload. The header can indicate that the multiple data packets are to be grouped together for routing, transmission or processing purposes.

FIG. 3 illustrates an example data processing system, in accordance with present implementations. The example data processing system (DPS) 300 can correspond to DPS 120. The DPS 120 can include one or more component or functionality of OFS 120. The DPS 300 can include at least one gateway engine 310 The DPS 300 can include at least one microservices engine 320. The DPS 300 can include at least one database 330. The DPS 300 can include at least one opportunity engine 340 The DPS 120 can include at least one security engine 350 The DPS 120 can include at least one system scheduler 360. The gateway engine 310 can include a health service gateway 312. The gateway engine can include a participant gateway 314.

The gateway engine 310 can generate, modify, block, transmit, or any combination thereof, for example, communication messages between at least the participant computing devices 232, the third party administrator devices 240, the microservices engine 320, the database 330, the opportunity engine 340, the security engine 350, and the system scheduler 360. The gateway engine 310 can include one or more operating systems, virtual machines, interpreters, or any combination thereof, for example, to generate, modify, block, transmit, or any combination thereof, for example, the communication messages. The gateway engine 310 can include one or more logical or electronic devices including but not limited to integrated circuits, logic gates, flip flops, gate arrays, programmable gate arrays, or any combination thereof, for example. It is to be understood that any electrical, electronic, or like devices, or components associated with the gateway engine 310 can also be associated with, integrated with, integrable with, replaced by, supplemented by, complemented by, or any combination thereof, for example, a system processor or any component thereof.

The health service gateway 312 can generate one or more communication messages compatible with one or more of the third party administrator devices, based on communication messages received from at least one of the microservices engine 320, the opportunity engine 340, the security engine 350, and the system scheduler 360. The health service gateway 312 is further operable to generate one or more communication messages compatible with at least one of the microservices engine 320, the opportunity engine 340, the security engine 350, and the system scheduler 360, based on communication messages received from one or more of the third party administrator devices 240. The health service gateway 312 can include at least one application programming interface (API) compatible with the third party administrator devices 240 and at least one of the microservices engine 320, the opportunity engine 340, the security engine 350, and the system scheduler 360. The health service gateway 312 can include at least one API to interface with third party administrator devices 240 associated with multiple third party administrator services. As one example, a third party administrator service can be a participant's health insurance service or a participant's prescription drug records service. The health service gateway 312 is configured to securely couple the security engine 350 to the third party administrator devices, in accordance with one or more security policies or health records standards. As one example, health records standards may be associated with Health Insurance Portability And Accountability Act (HIPAA) requirements or any combination thereof, for example.

The participant gateway 314 can generate one or more communication messages compatible with one or more of the participant computing devices 232, based on communication messages received from at least one of the microservices engine 320, the opportunity engine 340, the security engine 350, and the system scheduler 360. The participant gateway 316 is further operable to generate one or more communication messages compatible with one or more of the participant computing devices 232, based on communication messages received from at least one of the microservices engine 320, the opportunity engine 340, the security engine 350, and the system scheduler 360. The participant gateway 316 can include at least one API compatible with the participant computing devices 232 and at least one of the microservices engine 320, the opportunity engine 340, the security engine 350, and the system scheduler 360. The participant gateway 316 is configured to encapsulate at least one opportunity object received from the opportunity engine 320 and transmit the encapsulated opportunity object to one or more of the participant computing devices 232. The participant gateway 316 encapsulates an opportunity object in a JSON container, an encrypted package, a compressed package, or any combination thereof, for example. The participant gateway 316 transmits the opportunity object or the encapsulated opportunity object in accordance with a security policy.

The microservices engine 320 can generate, modify, block, transmit, or any combination thereof, for example, communication messages in accordance with at least one application programming interface (“API”) or any combination thereof, for example. In some implementations, an API can include at least one interface layer and at least one translation layer. The interface layer can include a command interface including at least one GET request, PUT request, or any combination thereof, for example. The interface layer further can include an HTTP, HTTPS or like transmission protocol by which the API communicates with one or more of the opportunity engine 340, the security engine 350, and the system scheduler 360. The translation layer can include one or more instructions to convert a first command in a first structure, format, configuration, state or any combination thereof, for example associated with a sending node, to a second command in a second structure, format, configuration, state or any combination thereof, for example associated with a receiving node. The sending node can be the third-party administrator devices 240 or the participant computing devices 232, and the receiving node can be at least one of the gateway engine 310 and the opportunity engine 340. Conversely, The receiving node can be the third-party administrator devices 240 or the participant computing devices 232, and the sending node can be at least one of the gateway engine 310 and the opportunity engine 340. The translation layer can include one or more of regular expressions, programmed code, or any combination thereof, for example. The translation layer can include one or more instructions to generate, modify, restrict, block, or any combination thereof, for example, one or more identifiers, headers, formats, structures, or any combination thereof, for example associated with one or more communication messages. As one example, the microservices engine 320 can include one or more API commands structures as secure web addresses operable to receive or send one or more parameters by GET or PUT commands, JSON objects, or any combination thereof, for example. The microservices engine 320 can generate one or more encapsulated communication message objects including or derived from the received or sent parameters. As one example, the microservices engine 320 can generate one or more binary communication messages based on text-based communication messages. The binary communication messages or the text-based communication messages include security structure compatible with one or more security operations of the security engine 350. As one example, security structure can include one or more dedicated header fields in communication messages modifiable, sortable, or any combination thereof, for example, by the security engine 350. The microservices engine 320 can include or is associated with one or more operating systems, virtual machines, interpreters, or any combination thereof, for example, to generate, modify, block, transmit, or any combination thereof, for example, the communication messages. The microservices engine 320 can include one or more logical or electronic devices including but not limited to integrated circuits, logic gates, flip flops, gate arrays, programmable gate arrays, or any combination thereof, for example. It is to be understood that any electrical, electronic, or like devices, or components associated with the microservices engine 320 can also be associated with, integrated with, integrable with, replaced by, supplemented by, complemented by, or any combination thereof, for example, a system processor or any component thereof.

The microservice engine 320 can include a plurality of API commands associated with participant objects, opportunity objects, and gateway objects. As one example, API commands associated with participant objects can include obtaining a summary of a participant profile, generating a participant profile, health conditions, pharmacies, prescriptions, and insurance account details associated with the participant. As another example, API commands associated with opportunity objects can include importing a “medicine cabinet” of prescriptions, importing pricing for prescriptions, attaching insurance carriers to a participant, modifying pricing for existing prescription orders, or any combination thereof, for example. As another example, API commands associated with gateway objects can include gateway configuration commands, third party vendor API wrappers, or any combination thereof, for example. In this example, the microservice engine 320 can include at its translation layer an API to convert instructions to a corresponding API of at least one third party administrator device 240. Thus, the microservice engine 320 achieves the technological solution of rapid, on-demand communication with multiple heterogeneous secure healthcare systems within a single automatically managed secure and distributed computing system.

The opportunity engine 340 can discover, audit, execute, or any combination thereof, for example, one or more opportunity objects. The opportunity engine 340 is operatively coupled to at least one of the participant database 332 and the opportunity database 334 to store, retrieve, modify, generate, link, delete, or any combination thereof, for example, one or more objects associated therewith. The opportunity engine 340 is operatively coupled to one or more of the third-party administrator devices 240 by at least one of the microservices engine 320, the opportunity engine 340, the security engine 350, and the system scheduler 360. The opportunity engine 340 can include one or more logical or electronic devices including but not limited to integrated circuits, logic gates, flip flops, gate arrays, programmable gate arrays, or any combination thereof, for example. It is to be understood that any electrical, electronic, or like devices, or components associated with the opportunity engine 340 can also be associated with, integrated with, integrable with, replaced by, supplemented by, complemented by, or any combination thereof, for example, a system processor or any component thereof.

The security engine 350 can restrict, regulate, modify, block, transmit, or any combination thereof, for example, one or more communication messages according to one or more transmission criteria or security criteria. The security engine 350 enforces one or more security policies including one or more security criteria. The security engine 350 applies a first security policy to communication messages associated with the participant communication devices 232. The first security policy can include a user level trust zone, associated with a low trust level. The security engine 350 applies a second security policy to communication messages associated with the third party administrator devices 240. The second security policy can include a third party level trust zone, associated with a low trust level. The security engine 350 applies a third security policy to communication messages associated with the microservices engine 310, the opportunity engine 340, and the system scheduler 360. The third security policy can include a cloud trust zone, associated with a medium trust level. It is to be understood that various security policies and various trust zones include, but are not limited to varying numbers and degrees of security encapsulation or any combination thereof, for example. The security encapsulation can include token validation, password validation, hardware key validation, symmetric encryption key validation, and asymmetric encryption key validation. The security engine 350 can include one or more logical or electronic devices including but not limited to integrated circuits, logic gates, flip flops, gate arrays, programmable gate arrays, or any combination thereof, for example. It is to be understood that any electrical, electronic, or like devices, or components associated with the security engine 350 can also be associated with, integrated with, integrable with, replaced by, supplemented by, complemented by, or any combination thereof, for example, a system processor or any component thereof.

The system scheduler 360 can generate, modify, block, transmit, or any combination thereof, for example, communication messages associated with opportunity objects, participant objects, and gateway objects in accordance with at least one transmission schedule or at least one batch processing criterion. The transmission schedule is a synchronous transmission schedule including at least one transmission interval between transmission times. The system scheduler 360 instructs, commands, controls, or any combination thereof, for example, at least one of the gateway engine 310 and the security engine 350 to transmit, generate, or any combination thereof, for example, one or more communication messages associated with one or more opportunity objects, participant objects, and gateway objects at a transmission time. In some implementations, a batch processing criterion can include a connectivity condition between at least one of the participant computing devices 232 and the data processing system 120. The system scheduler 360 enters an asynchronous mode in response to determining that connectivity with one or more particular participant computing devices 240 is below a connectivity threshold. The batch processing criterion can include the connectivity threshold. As one example, a connectivity threshold can be a minimum lag, bandwidth, uptime, or any combination thereof, for example associated with a minimum ability to transmit one or more opportunity objects. The system scheduler 360 can include one or more queues to asynchronously store, buffer, or any combination thereof, for example any communication messages that cannot be transmitted at a particular transmission time due to failure to satisfy a connectivity threshold or satisfying a batch processing criterion. The system scheduler 360 is selectably configurable into a synchronous mode, an asynchronous mode, or both. The system scheduler 360 is selectably configurable by at least one API associated therewith.

FIG. 4 illustrates an example participant database system further to the example data processing system of FIG. 3, in accordance with present implementations. The example participant database system 400 corresponds to the participant database 332. The example participant database system 400 can include at least one of a participant object 410, an insurance object 420, a prescription object 430, a pharmacy object 440, a participant profile object 450, and a drug object 460. It is to be understood that the example participant database system can support an arbitrary number of objects dependent only upon extrinsic characteristics of the example participant database system. As one example, extrinsic characteristics of the example participant database system can include a storage capacity thereof.

The participant object 410 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a participant of a health support system or any combination thereof, for example. The participant object can include at least one object identifier 412, timestamp 414, participant key 416, geolocation monitor 418, insurance linker 422, prescription linker 432, pharmacy linker 442, participant profile linker 452, and opportunity object linker 402.

The object identifier 412 contains one or more characteristics associated with a user of the data processing system 120. The object identifier can include one or more of a database key identifying the participant object, a participant identifier associated with a health service, a participant identifier associated with a participant computing device, or any combination thereof, for example. As one example, the participant identifier associated with the health service can include at least one an indication of an association between a participant and a particular health service provider, and an association between the participant and a particular health account provider. As another example, the participant identifier associated with the health service can include an indication that the participant is associated with a particular type of health service or health account. As another example, health account type can be an HSA account. The timestamp 414 can indicate one or more times of critical events. The timestamp 414 can include one or more UNIX timestamps. The timestamp 414 can include at least one of a creation timestamp, a modification timestamp. The modification timestamp is responsive to any action to the participant object 410 by the opportunity engine 420 or any component thereof.

The participant key 416 contains a key based on multiple identifiers associated with a participant. The participant key 416 is based on at least one of an account code, an employer identifier and an employee identifier associated with the participant and the health service associated with the participant. The participant key 416 is encrypted, hashed, or any combination thereof, for example. The participant key 416 is available as a validation key for authorization through the first, second or third security policies.

The geolocation monitor 418 contains a geolocation associated with the participant associated with the participant object 410. The geolocation monitor 418 stores one or more latitude and longitude values to designate a geolocation. The geolocation monitor 418 obtains a geolocation from a participant computing device 240 associated with the participant object 410. The geolocation monitor 418 obtains the geolocation by the participant gateway 316. The event control engine 310 can modify the geolocation monitor 418. The geolocation monitor 418 receives a geolocation on a constantly updating basis. Alternatively, The geolocation monitor 418 receives the geolocation on a scheduled basis in response to actions by the system scheduler 318.

The insurance linker 422 contains a dynamic link to the insurance object 420. The insurance linker 422 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the insurance object 420 associated with the participant object 410. The insurance linker 422 associates the insurance object 420 with the participant object 410 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410.

The prescription linker 432 contains a dynamic link to the prescription object 430. The prescription linker 432 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the prescription object 430 associated with the participant object 410. The prescription linker 432 associates the prescription object 430 with the participant object 410 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410.

The pharmacy linker 442 contains a dynamic link to the pharmacy object 440. The pharmacy linker 442 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the pharmacy object 440 associated with the participant object 410. The pharmacy linker 442 associates the pharmacy object 440 with the participant object 410 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410.

The participant profile linker 452 contains a dynamic link to the participant profile object 450. The participant profile linker 452 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the participant profile object 450 associated with the participant object 410. The participant profile linker 452 associates the participant profile object 450 with the participant object 410 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410.

The opportunity object linker 402 contains a dynamic link to an opportunity object 510. The opportunity object linker 402 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the opportunity object 510 associated with the participant object 410. The participant profile linker 452 associates the participant profile object 450 with the participant object 410 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410.

The insurance object 420 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a participant of a health support system or any combination thereof, for example. The insurance object is associated with, represents, or any combination thereof, for example, characteristics, variables, executables, or any combination thereof, for example associated with a health support account, a support account, or any combination thereof, for example. The insurance object 420 is configured to execute to facilitate execution of one or more instructions to a health support account, support account, or any combination thereof, for example. The insurance object 420 can include an object identifier 424 and a provider encapsulator 426. The object identifier 424 contains one or more characteristics associated with an insurance entity associated with the participant object 410 of the data processing system 120. The object identifier 424 contains or can include one or more blocks, links, executables, or any combination thereof, for example associated with at least one of the participant object 410 or a participant associated with the participant object 410. The provider encapsulator 426 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a health support system or any combination thereof, for example. The object identifier 424 can include one or more identifiers associated with a health support account. As one example, the object identifier 424 can include one or more of a health insurance carrier identification block, a health insurance group identification block, and a health insurance UUID identification block.

The prescription object 430 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a pharmaceutical system, pharmaceutical entity, pharmaceutical account, pharmaceutical, health metric, biological metric, or any combination thereof, for example, associated with the participant object 410 or a participant associated with the participant object 410. The prescription object 430 can include an object identifier 434, a prescription encapsulator 436, a participant key 416, a drug linker 462, and a pharmacy linker 442. The prescription object can include corresponding instances, references, or any combination thereof, for example of one or more elements or components associated with corresponding objects of the example participant database system. The object identifier 434 contains one or more characteristics associated with a pharmaceutical entity associated with the participant object 410 of the data processing system 120. The object identifier 434 contains or can include one or more blocks, links, executables, or any combination thereof, for example associated with at least one of the participant object 410 or a participant associated with the participant object 410.

The prescription encapsulator 436 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with at least one quantity, metric, volume, amount, mass, time, dosage, or any combination thereof, for example of at least one drug object 460. The prescription encapsulator is configured to encapsulate at least one personally-identifiable health record within a secure wrapper. The prescription object 430 is configured to securely encapsulate at least one record of any type with the participant key 416. The participant key 416 decrypts or any combination thereof, for example, either alone or in combination with additional security components, the prescription encapsulator 436 or any wrapper or any combination thereof, for example associated therewith.

The participant key 438 contains a key based on multiple identifiers associated with a participant. The participant key 438 corresponds to the participant key 416. The participant key 438 is a copy, reference, link, or any combination thereof, for example, to the participant key 416. The prescription object is configured to validate or facilitate validation of information, executables, parameters, or any combination thereof, for example, contained in or associated with the participant object 410, the insurance object 420, or the prescription object 430.

The drug linker 462 contains a dynamic link to the drug object 460. The drug linker 462 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the drug object 460 associated with the prescription object 430. The drug linker 462 associates the prescription object 430 with the drug object 460 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410. The drug linker 462 generates a link, reference, or any combination thereof, for example, to at least one drug object 460 within a prescription associated with a participant object 410. As one example, the drug linker 462 can generate and maintain a link to a drug object statically or dynamically based on a drug provider by a health support service, support service, or any combination thereof, for example.

The pharmacy linker 442 contains a dynamic link to the pharmacy object 440. The pharmacy linker 442 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the pharmacy object 440 associated with the prescription object 430. The pharmacy linker 442 associates the prescription object 430 with the pharmacy object 440 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410. The pharmacy linker 442 generates a link, reference, or any combination thereof, for example to at least one pharmacy object 440 within at least one pharmacy selection criterion associated with a participant object 410. As one example, the pharmacy linker 440 can generate and maintain a link to a pharmacy object statically or dynamically based on a restriction or preference selection by a participant, a restriction or preference by a health support service, support service, or any combination thereof, for example.

The pharmacy object 440 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a pharmacy system, pharmacy entity, pharmacy account, health metric, consumer metric, or any combination thereof, for example, associated with the participant object 410 or a participant associated with the participant object 410. The pharmacy object 440 can include an object identifier 444, a location identifier 446, and a geolocation identifier 448. The object identifier 444 contains one or more characteristics associated with a pharmacy associated with the participant object 410 of the data processing system 120. The object identifier 444 contains or can include one or more blocks, links, executables, or any combination thereof, for example associated with at least one of the participant object 410 or a participant associated with the participant object 410. The location identifier 446 contains one or more characteristics associated with a pharmacy location associated with the participant object 410 of the data processing system 120. The location identifier 446 can include one or more addresses, pharmacy location codes, phone numbers, or any combination thereof, for example. The geolocation identifier 448 contains one or more characteristics associated with a pharmacy geolocation associated with the participant object 410 of the data processing system 120. The location identifier 446 can include one or more latitude coordinates, longitude coordinates, spherical coordinates, Global Positioning System (“GPS”) coordinates, pathfinding routes, or any combination thereof, for example.

The participant profile object 450 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a health metric, consumer metric, diagnostic assessment, prognostic assessment, health device interface, or any combination thereof, for example, associated with the participant object 410 or a participant associated with the participant object 410. The participant profile object can include an object identifier 454 and a diagnostic encapsulator 456. The object identifier 454 contains one or more characteristics associated with a pharmacy associated with the participant object 410 of the data processing system 120. The object identifier 454 contains or can include one or more blocks, links, executables, or any combination thereof, for example associated with at least one of the participant object 410 or a participant associated with the participant object 410.

The diagnostic encapsulator 456 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with at least one characteristic of the participant object 410 or a participant associated with the participant object 410. As one example, diagnostic encapsulator 456 can include at least one of medical history, prescription history, current medical conditions, family medical history, evaluation charts, or any combination thereof, for example associated with a participant object 410 or a participant associated with the participant object 410. The diagnostic encapsulator 456 is configured to encapsulate at least one personally-identifiable health record within a secure wrapper. The participant profile object 430 is configured to securely encapsulate at least one record of any type with at least one of the participant key 416 and 438. In some implementations, at least one of the participant key 416 and 438 decrypts or any combination thereof, for example, either alone or in combination with additional security components, the prescription encapsulator 436 or any wrapper or any combination thereof, for example associated therewith. The diagnostic encapsulator 456 is configured to secure information associated therewith or contained therein in accordance with one or more diagnostic security protocols. As one example a diagnostic security protocol can include a restriction on access, decryption, or any combination thereof, for example, based on a HIPAA or like restriction.

The drug object 460 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a drug, pharmaceutical, chemical, biochemical, composition, substance, element, molecule, or any combination thereof, for example associated with at least one of a pharmacy object 440 and a prescription object 430. The drug object 460 is generated based on a database system, inventory system, sales system, or any combination thereof, for example associated with at least one of a pharmacy system, health support system, health insurance provider, or any combination thereof, for example. As one example, the drug object 460 is generated based on available drugs at one or more pharmacies associated with the participant and included in at least one prescription object associated with the participant. As another example, the drug object 460 is generated based on the diagnostic encapsulator to include drugs associated with a particular health condition of a participant associated with the participant object 410. The drug object can include an object identifier 464 and a drug encapsulator 466. The object identifier 464 contains one or more characteristics associated with a drug object associated with at least one of the participant object 410 and the pharmacy object 440. The object identifier 454 contains or can include one or more blocks, links, executables, or any combination thereof, for example associated with at least one of the participant object 410 or a participant associated with the participant object 410.

The drug encapsulator 466 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with at least one characteristic of the drug object 460. As one example, the drug encapsulator 466 can include at least one of a chemical composition, commercial product identifier, brand identifier, generic product identifier, or any combination thereof, for example. The drug encapsulator 466 is configured to encapsulate at least one personally-identifiable health record within a secure wrapper. The drug object 460 is configured to securely encapsulate at least one record of any type with at least one of the participant key 416 and 438. In some implementations, at least one of the participant key 416 and 438 decrypts or any combination thereof, for example, either alone or in combination with additional security components, the drug encapsulator 466 or any wrapper or any combination thereof, for example associated therewith. The drug encapsulator 466 is configured to secure information associated therewith or contained therein in accordance with one or more diagnostic security protocols. As one example a diagnostic security protocol can include a restriction on access, decryption, or any combination thereof, for example, based on a HIPAA or like restriction.

FIG. 5 illustrates an example opportunity database system further to the example data processing system of FIG. 3, in accordance with present implementations. The example opportunity database system 500 corresponds to the opportunity database 334. The example opportunity database system 500 can include at least one of an opportunity object 510, an opportunity type object 520, an opportunity action 530, a prescription action object 540, and an account action object 550.

The opportunity object 510 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a participant of a health support system or any combination thereof, for example. The opportunity object 510 is associated with, represents, or any combination thereof, for example, characteristics, variables, executables, or any combination thereof, for example associated with a health support account, a support account, or any combination thereof, for example. The opportunity object 510 is configured to execute to facilitate execution of one or more instructions to a health support account, support account, or any combination thereof, for example. The opportunity object 510 is configured to execute a financial transaction across a plurality of secure and heterogeneous database system or commercial computing systems. As one example, the opportunity object 510 is configured to execute a transaction with a pharmacy system to obtain a pharmaceutical prescription, including secure patient information and secure financial information of a participant associated with a participant object 410. In this example, the opportunity object 510 achieves the technical solution of secure digital communication across multiple secure systems involving both financial security and patient care security protocols. The opportunity object 510 can include an object identifier 512, a type linker 522, and an action linker 532. The object identifier 512 contains one or more characteristics associated with the opportunity object 510. The object identifier 512 contains or can include one or more blocks, links, executables, or any combination thereof, for example associated with opportunity object 510.

The type linker 522 contains a dynamic link to the opportunity type object 520. The type linker 522 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the opportunity type object 520 associated with the opportunity object 510. The type linker 522 associates the opportunity object 510 with the opportunity type object 520 in accordance with one or more of an import process of participant information from one or more third party administrator devices 240, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410.

The action linker 532 contains a dynamic link to the opportunity action object 530. The action linker 532 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to one or more opportunity action objects 530 associated with the opportunity object 510. The action linker 532 associates the opportunity object 510 with the opportunity action object 530 in accordance with an import process of participant information from one or more third party administrator devices 240 The action linker 532 associates the opportunity object 510 with the opportunity action object 530 in accordance with a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410. The action linker 532 associates the opportunity object 510 with the opportunity action object 530 in accordance with a scheduled updated initiated by a scheduling process or a batching process.

The opportunity type object 520 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with a participant of a health support system or any combination thereof, for example. The opportunity object 510 is associated with, represents, or any combination thereof, for example, characteristics, variables, executables, or any combination thereof, for example associated with an opportunity. As one example, the opportunity type object can include at least one value, metric, executable, link, or any combination thereof, for example associated with a time-sensitive opportunity. The opportunity type object 520 can include an object identifier 522 and a point module 524. The object identifier 522 contains one or more characteristics associated with the opportunity type object 510. The object identifier 522 can include one or more blocks, links, executables, or any combination thereof, for example associated with opportunity type object 522.

The point module 524 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with an execution value of an opportunity object associated with the opportunity type object 520. As one example, the point module 524 can include at least one value, metric, executable, link, or any combination thereof, for example associated with a quantitative point value for executing the opportunity object 510. The quantitative point value dynamically changes based on one or more opportunity or participant metrics, factors or any combination thereof, for example. As one example, the quantitative point value decreases toward zero as a current timestamp approaches a timestamp threshold.

The opportunity action object 530 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example to execute or facilitate execution of at least one action based on at least one of the prescription action object 540 and the account action object 550. The opportunity action object 530 can include one or more instructions, restrictions, security policies, interfaces, or any combination thereof, for example to execute or facilitate execution of at least one of the prescription action object 540 and the account action object 550. The opportunity action object 530 include an action associated with an application programming interface (“API”) of the data processing system 120. The opportunity action objects is associated with an API call through one or more gateways of the data processing system 120. The API call can be a call to conduct actions including SwitchtoDirectDeposit, SetUpMedicineCabinet, ChangeElectronicDelivery, AttachInsuranceCarrier, AddMobilePhone, SignUpForAlerts, SignUpForElectronicTaxForms, and EnableLocationTracking. The API call is compatible with an API provided by, controlled by, generated by, or any combination thereof, for example, the microservices engine 320.

The prescription action object 540 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example to execute or facilitate execution of at least one action based on the opportunity action object 540. The prescription action object 540 can include one or more instructions, restrictions, security policies, interfaces, or any combination thereof, for example to modify the state of at least one medical records system associated with the prescription action object 540. As one example, a medical records system can include a pharmacy system, a health support system, a health insurance system, or any combination thereof, for example. The prescription action object 540 include a cost encapsulator 542, the prescription linker 432, and the pharmacy linker 442.

The cost encapsulator 542 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with at least one financial value, metric, or any combination thereof, for example associated with the prescription object 430. As one example, the cost encapsulator 542 can include at least one of a price, pricing table, pricing modifier associated with at least one of the prescription object 430, the pharmacy object 440, and the drug object 460. The cost encapsulator 542 is configured to generate at least one modification to a cost value, metric, or any combination thereof, for example associated with the prescription object 430, the pharmacy object 440, and the drug object 460. As one example, the cost encapsulator 542 is configured to generate a LongtermSavings value indicating a difference between cost for a prescription upon execution of an opportunity as compared to not executing the opportunity. It is to be understood that the cost encapsulator 542 is configured to achieve the technical solution of generating the LongtermSavings value based on multiple factors including multiple drugs that may be subject to cost modification based on multiple prescriptions from multiple health support systems and multiple pharmacy systems. The cost encapsulator 542 is configured to generate the LongtermSavings value with respect to a plurality of participants based on individualized records.

The account action object 550 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example to execute or facilitate execution of at least one action based on the opportunity action object 540. The account action object 550 can include one or more instructions, restrictions, security policies, interfaces, or any combination thereof, for example to modify the state of at least one financial account system associated with the account action object 550. As one example, a financial account system can include a bank account, an HSA account, a flexible spending account (“FSA”) or any combination thereof, for example. The account action object 550 can include an account identifier 552 and a cost encapsulator 554. The account action object 550 can include an account identifier 552 and a cost encapsulator 554. The account identifier 552 contains one or more characteristics associated with the financial account associated with the opportunity action object 530. The account identifier 552 can include one or more blocks, links, executables, or any combination thereof, for example associated with a financial account system. As one example, the account identifier 552 is or encapsulates a financial account number, a financial account routing number, a financial account authorization code, a financial account authorization token, a financial account link, or any combination thereof, for example.

The cost encapsulator 554 is configured to encapsulate at least one executable, module, link, or any combination thereof, for example associated with at least one financial value, metric, or any combination thereof, for example associated with the account identifier 552. As one example, the cost encapsulator 542 can include at least one of a financial contribution amount, financial payment amount, financial credit amount, financial debit amount, or any combination thereof, for example associated with the account identifier 552. The cost encapsulator 554 is configured to generate at least one modification to a cost value, metric, or any combination thereof, for example associated with the account identifier 552. As one example, the cost encapsulator 542 is configured to generate a MaxOutContributions value instructing a financial account system to increase a payment to the financial account according to one or more threshold criteria contained in the account identifier 552. It is to be understood that the cost encapsulator 554 is configured to achieve the technical solution of generating the MaxOutContributions value based on secure direct communication with a financial account system.

FIG. 6 illustrates an example gateway database system further to the example data processing system of FIG. 3, in accordance with present implementations. The example gateway database system 600 corresponds to the opportunity database 334. As illustrated by way of example in FIG. 6, an example gateway database system 600 can include a gateway event object 610, a gateway request object 620, a gateway response object 630, an execution target object 640, a result object 650, and a header object 660.

The gateway event object 610 contains at least one link, reference, or any combination thereof, for example to one or more opportunity objects. The gateway event object 610 can control responses to events received at the gateway engine 310 based on event type. The gateway event object 610 is generated, modified, configured, deleted, or any combination thereof, for example, based on an API call by the microservice engine 320. The gateway event object 610 links at least one event type with at least one corresponding opportunity object. Thus, The gateway even object 610 links one or more opportunity objects to one or more events operable to trigger a response at or by those linked opportunity objects. The gateway event object 610 can include an object identifier 612, timestamp 614, a microservice encapsulator 616, and an opportunity encapsulator 618. The object identifier 612 contains one or more characteristics associated with an event detected at the gateway engine 310 of the data processing system 120. The object identifier 612 can include one or more blocks, links, executables, or any combination thereof, for example associated with the gateway event object 610. The timestamp 614 can indicate one or more times of critical events. The timestamp 614 can include one or more UNIX timestamps. The timestamp 614 can include at least one of a creation timestamp, and a modification timestamp. The modification timestamp is responsive to any action to the gateway event object 610 by at least one of the gateway engine 310 and microservice engine 320.

The microservice encapsulator 616 contains at least one instruction, identifier, command, key, or any combination thereof, for example associated with at least one microservice of the microservice engine 320. The microservice encapsulator 616 can include at least one API command associated with an API of the microservice engine 320. As one example, the microservice encapsulator 616 can include at least one web address, link, universal resource locator (URL), or any combination thereof, for example, corresponding to an API command of the microservice engine 320. As another example, the microservice encapsulator 616 can include at least one web address, link, universal resource locator (URL), or any combination thereof, for example, including at least one parameter, argument, or any combination thereof, for example, corresponding to an API command of the microservice engine 320 operable to accept one or more parameters, arguments or any combination thereof, for example. As another example, the microservice encapsulator 616 contains one or more regular expressions or any combination thereof, for example corresponding to at least a portion of an API command, parameter, argument, or any combination thereof, for example, of the microservice engine 320.

The opportunity encapsulator 618 at least one instruction, identifier, command, key, or any combination thereof, for example associated with at least one opportunity object of the opportunity database 334. The opportunity encapsulator 618 can include a link, reference, identifier, or any combination thereof, for example, to at least one opportunity object. Alternatively, The opportunity encapsulator 618 can include a copy, duplicate, partial copy, partial duplicate, or any combination thereof, for example associated with at least one opportunity object. Thus, The opportunity encapsulator 618 associates the opportunity event object 610 with at least one opportunity object.

The gateway request object 620 contains at least one link, reference, or any combination thereof, for example to at least one engine of the data processing system 120. The gateway request object 620 can generate, receive, modify, or any combination thereof, for example, at least one operation executable by at least one of the gateway engine 310, the microservices engine 320, the opportunity engine 340, and the security engine 350. The gateway request object 620 can include an object identifier 622, a microservice encapsulator 616, and an execution target linker 624. The object identifier 622 contains one or more characteristics associated with a request received at, generated by, or any combination thereof, for example, the gateway engine 310 of the data processing system 120. The object identifier 622 can include one or more blocks, links, executables, or any combination thereof, for example associated with the gateway event object 610.

The execution target linker 624 contains a dynamic link to the execution target object 640. The execution target linker 624 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the execution target object 640 associated with the gateway request object 620. The execution target linker 624 associates the gateway request object 620 with the execution target object 640 in accordance with one or more of a configuration process of the gateway engine 310, or a selection, interaction, or any combination thereof, for example received from a participant computing device 232 associated with the participant object 410. The execution target linker 624 generates a link, reference, or any combination thereof, for example to at least one execution target object 640 dynamically modifiable based on the state of at least one of a participant object 410 and a participant profile object 450. As one example, the execution target linker 624 can generate and maintain a link to an execution target object statically or dynamically based on a service tier supporting execution at one or more predetermined engines of the data processing system 120.

The gateway response object 630 contains at least one record of characteristics associated with an executed response to the gateway request object 620. The gateway response object 630 can include an encapsulator operable to contain all input to a target execution engine and all output from the target execution engine associated with a particular gateway request object. The gateway response object 630 can include an object identifier 632, timestamp 634, a parameter linker 636, and a result linker 638. The object identifier 632 contains one or more characteristics associated with an event detected at the gateway engine 310 of the data processing system 120. The object identifier 632 can include one or more blocks, links, executables, or any combination thereof, for example associated with the gateway response object 630. The timestamp 634 can indicate one or more times of critical events. The timestamp 634 can include one or more UNIX timestamps. The timestamp 634 can include at least one of a creation timestamp, and a modification timestamp. The modification timestamp is responsive to any action to the gateway event object 610 by at least one of the gateway engine 310 and microservice engine 320.

The parameter linker 636 contains a dynamic link to one or more parameters or any combination thereof, for example associated with the gateway response object 640. The parameter linker 636 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the parameters in response to a transmission of the execution target object 640 to one or more of the gateway engine 310, the microservice engine 320, the opportunity engine 340, and the security engine 350. The parameter linker 636 associates the parameters with the gateway response object 640 in accordance with one or more of a configuration process of the gateway engine 310, or a generation or modification of the gateway response object 640.

The result linker 638 contains a dynamic link to the result object 650. The result linker 638 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the result object 650 associated with the gateway response object 630. The result linker 638 associates the gateway response object 630 with the result object 650 in accordance with one or more of a configuration process of the gateway engine 310, or a selection, interaction, or an execution of at least one opportunity object associated with the execution target object 640.

The execution target object 640 contains at least one instruction, identifier, command, key, or any combination thereof, for example associated with at least one of the gateway engine 310, the microservice engine 320. The execution target object 640 controls, triggers, initiates, restricts, or any combination thereof, for example, execution of one or more opportunity objects, gateway objects, or any combination thereof, for example. As one example, the execution target object 640 can direct a gateway request mapping associated with a particular opportunity object to the opportunity engine 340 for execution, modification, deletion, or any combination thereof, for example, of the opportunity object. In some implementations, execution target object 640 can include an object identifier 642, a payload encapsulator 644, a parameter linker 646, and a header linker 648. The object identifier 642 contains one or more characteristics associated with an event detected at the gateway engine 310 of the data processing system 120. The object identifier 642 can include one or more blocks, links, executables, or any combination thereof, for example associated with the execution target object 640.

The payload encapsulator 644 contains one or more objects, references, links, or any combination thereof, for example, associated with execution of the execution target object 640. As one example, the payload encapsulator 644 can include one or more payload objects returned in response to execution according to the execution target object 640. As one example, payload objects can include JSON, binary executable, database objects, or any combination thereof, for example. The size of the payload objects can exceed a predetermined size threshold for copying. Thus, The payload encapsulator 644 can replace a copy of the payload object with a reference to the payload object at another payload encapsulator. The predetermined size threshold can be an absolute size threshold or a relative size threshold. As one example, an absolute size threshold can be 1 MB, MiB, or any combination thereof, for example. As another example, a relative size threshold can correspond to a proportion of a predetermined capacity of database 330. In this example, the predetermined capacity of database 330 can be 0.1% of the capacity of the database 330, and payload encapsulator 644 can be configured to store a reference to the payload object if the payload object exceeds be 0.1% of the capacity of the database 330 in size.

The parameter linker 646 contains a dynamic link to one or more parameters or any combination thereof, for example associated with the execution target object 640. The parameter linker 646 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the parameters in response to a transmission of the execution target object 640 to one or more of the gateway engine 310, the microservice engine 320, the opportunity engine 340, and the security engine 350. The parameter linker 646 associates the parameters with the execution target object 640 in accordance with one or more of a configuration process of the gateway engine 310, or an execution of at least one opportunity object associated with the execution target object 640.

The header linker 648 contains a dynamic link to one or more parameters or any combination thereof, for example associated with the header object 660. The header linker 648 can generate, store, or any combination thereof, for example, a link, reference, or any combination thereof, for example to the header object 660 in response to a generation of the gateway response object 630, or a transmission of the execution target object 640 to one or more of the gateway engine 310, the microservice engine 320, the opportunity engine 340, and the security engine 350. The header linker 648 associates the parameters with the header object 660 in accordance with one or more of a configuration process of the gateway engine 310, or an execution of at least one opportunity object associated with the execution target object 640.

The result object 650 contains at least one result returned in response to execution of at least one of an opportunity object and a gateway request object. The result object 650 can include a payload encapsulator 652 and a header linker 648. The payload encapsulator 652 contains one or more objects, references, links, or any combination thereof, for example, associated with execution of the execution target object 640. The payload encapsulator 652 corresponds to the payload encapsulator 644. The payload encapsulator 652 can include a reference to the payload encapsulator 644 in accordance with one or more thresholds associated therewith. Alternatively, The payload encapsulator 644 can include a reference to the payload encapsulator 652 in accordance with one or more thresholds associated therewith.

The header object 660 contains at least one object associated with identifying or executing an opportunity object or a gateway object. The header object 660 can include a key encapsulator 662 and a parameter encapsulator 664.

The key encapsulator 662 contains at least one key associated with at least one participant object, opportunity object, or gateway object. The key encapsulator 662 contains a key required by the security engine 350. The security engine 350 validates the header object 660 associated with the execution target object 640 before allowing execution according to the execution target object 640. As one example, the security engine 350 can block execution of the execution target object 640 if the security engine 350 determines that the key contained in key encapsulator 662 is invalid, or corresponds to a security policy incompatible with the execution target object 640, or the parameters thereof. In this example, the security engine 350 can permit execution if the key contained in key encapsulator 662 is valid, or corresponds to a security policy compatible with the execution target object 640, or the parameters thereof.

The parameter encapsulator 664 contains one or more parameters or any combination thereof, for example associated with the execution target object 640. The parameter encapsulator 664 can generate, store, or any combination thereof, for example, a copy of the parameters in response to a transmission of the execution target object 640 to one or more of the gateway engine 310, the microservice engine 320, the opportunity engine 340, and the security engine 350. In some implementations, parameters of the parameter encapsulator 664 corresponds to parameters associated with the parameter linker 636. The parameter encapsulator 664 contains parameters mirrored, copied, or any combination thereof, for example from parameter linker 636 or in parallel with generation, modification, or any combination thereof, for example, of parameters at the parameter linker 636.

FIG. 7 illustrates an example electronic device associated with an example data processing system, in accordance with present implementations. The example electronic device 700 can include a processor, memory device, and display device to generate a graphical user interface, and a communication interface to communication with the data processing system as discussed above with respect to FIGS. 1A-D and 2. The example electronic device can include an opportunity summary region 702, a score summary region 704, an account action object region 606, and an opportunity list region 710. The example electronic device 700 can generate a graphical user interface (“GUI”) representing, displaying, or any combination thereof, for example, one or more of objects of FIGS. 4 and 5. In some implementations, The example electronic device 700 can include a GUI associated with a mobile operating system. In some implementations, The example electronic device 700 is further operable to receive selection, input, or any combination thereof, for example from a touch-based input system disposed thereon, therewith, or any combination thereof, for example. The touch-based input system is a capacitive or a resistive touch interface. In some implementations, that the mobile interface can include a presentation device including but not limited to an LCD, LED, OLED or any combination thereof, for example.

The opportunity summary region 702 is configured to present at least one metric associated with one or more opportunity objects available for selection at the example electronic device 700. The opportunity summary region 702 presents a total number of available opportunity objects for selection. The opportunity summary region 702 presents a total number of available opportunity objects that have not yet been executed.

The score summary region 704 is configured to present at least one metric associated with one or more opportunity objects available for election at the example electronic device 700. The score summary region 704 presents at least one execution value associated with the point module 524. The score summary region 704 presents an aggregation of a plurality of execution values associated with a corresponding plurality of point modules each associated with a particular point value. The opportunity list region 710 is configured to present at least one opportunity object 510 as a selectable GUI element. The opportunity list region can include one or more opportunity objects 712. The opportunity objects 712 each correspond to a distinct opportunity object 510 of a plurality available at the opportunity database 334.

FIG. 8 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, in accordance with present implementations. The method 800 can be performed by one or more component, system, device or module depicted in FIGS. 1A-7, including for example, a DPS or device 700.

At step 810, the example system trains a machine learning model with historical data. Step 810 can include at least one of steps 812 and 814. At step 812, the example system trains a machine learning model with historical data from one or more opportunities or opportunity objects, for example. At step 814, the example system trains a machine learning model with opportunities from one or more third party applications or systems, for example. The method 800 then continues to step 820.

At step 820, the example system identifies at least one third party application from one or more third party applications. Step 820 can include at least one of steps 822, 824 and 826. At step 822, the example system identifies at least one third party application among one or more third party applications with at least one corresponding application programming interface (API). At step 824, the example system identifies at least one third party application by an interface of the example system or the data processing system of the example system. At step 826, the example system identifies a particular third party application different from another third party application. Both the particular third party application and the other third party application can be selected or selectable, for example, from the one or more third party applications. The method 800 then continues to step 830.

At step 830, the example system crawls a web page of a provider of the third party application. The example system can crawl a web page by retrieving and parsing the web page to identify one or more portions, fields, components, factors, or values therein, for example. Step 830 can include step 832. At step 832, the example system identifies a candidate opportunity on a web page. It is to be understood that the example system can be configured to crawl, parse, or any combination thereof, for example, any remote document content, and is not limited to a web page. The method 800 then continues to step 902.

FIG. 9 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, further to the method of FIG. 8, in accordance with present implementations. The method 900 can be performed by one or more component, system, device or module depicted in FIGS. 1A-7, including for example, a DPS or device 700. The method 900 begins at step 902. The method 900 then continues to step 910.

At step 910, the example system determines to query at least one third party application responsive to at least one trigger condition. As one example, a trigger condition can be a posting of new opportunities, or an expiration of a time period associated with a polling period. Step 910 can include at least one of steps 912, 914 and 916. At step 912, the example system determines to query at least one third party application responsive to a crawling operation. At step 914, the example system selects a first query template for a first API compatible with a first third party application. At step 916, the example system selects a second query template for a second API compatible with a second third party application. The method 900 then continues to step 920.

At step 920, the example system constructs a first query associated with a first third party application. As one example, the example system can generate a first query based on parameters of the first API. Step 920 can include at least one of steps 922, 924 and 926. At step 922, the example system constructs a second query associated with a second third party application, where the second query is different from the first query. The second query can be different from the first query. At step 924, the example system constructs one or more of the first query and the second query with one or more corresponding authorizing credentials for receiving a response. At step 926, the example system constructs one or more of the first query and the second query for receiving a response associated with an opportunity event. The method 900 then continues to step 1002.

FIG. 10 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, further to the method of FIG. 9, in accordance with present implementations. The method 1000 can be performed by one or more component, system, device or module depicted in FIGS. 1A-7, including for example, a DPS or device 700. The method 1000 begins at step 1002. The method 1000 then continues to step 1010.

At step 1010, the example system determines to transmit a query based at least partially on a location associated with a computing device. The location associated with the computing device can be an address, geolocation, coordinate, geofence, or any combination thereof, for example. The computing device can be a mobile device associated with, carried by, or co-located with a participant. Step 1010 can include at least one of steps 1012 and 1014. At step 1012, the example system determines to transit a query at least partially by a participant object input to a machine learning model. The input can include one or more metrics compatible with input to the machine learning model and based on one or more values, for example, associated with a participant object. At step 1014, the example system determines to transmit based at least partially on the output of a machine learning model. The method 1000 then continues to step 1020.

At step 1020, the example system transmits a query to a third party application. Step 1020 can include step 1022. At step 1022, the example system transmits a query constructed by a template compatible with an API associated with the third party application. The method 1000 then continues to step 1030. At step 1030, the example system receives a response associated with an opportunity event from the third party application. The method 1000 then continues to step 1040. At step 1040, the example system parses a received response to identify an opportunity event. The method 1000 then continues to step 1050.

At step 1050, the example system constructs an opportunity object based on the identified opportunity event. The method 1000 then continues to step 1102.

FIG. 11 illustrates an example method of digital feed generation by a micro-services architecture integrating heterogeneous nodes, further to the method of FIG. 10, in accordance with present implementations. The method 1100 can be performed by one or more component, system, device or module depicted in FIGS. 1A-7, including for example, a DPS or device 700. The method 1100 begins at step 1102. The method 1100 then continues to step 1110.

At step 1110, the example system selects a participant object satisfying one or more parameters associated with an opportunity event. As one example, the example system can select a participant object for a participant enrolled with a third party provider associated with the opportunity event. The method 1100 then continues to step 1120.

At step 1120, the example system provides an indication of the opportunity objects to at least one computing device. As one example, an indication can be a push notification, a text message, a telephone call, or any combination thereof, for example. Step 1122 can include step 1122. At step 1122, the example system provides an indication of the opportunity objects to at least one computing device associated with a participant object. The method 1100 then continues to step 1130.

At step 1130, the example system transmits at least one opportunity object for presentation via a computing device. The computing device can be associated with the participant having a participant object associated with opportunity object. The method 1100 then continues to step 1140. At step 1140, the example system receives an indication to execute an opportunity object via a computing device. As one example, the indication can be an execution instruction received in response to a click or touch event, for example, at the computing device. The method 1100 then continues to step 1150.

At step 1150, the example system authorizes execution of the opportunity object by the participant object. As one example, authorization can be an instruction approving execution of one or more operations at a third party system, where the operations correspond to the opportunity object. The method 1100 can end at step 1150.

It should be understood that the systems described above can provide multiple ones of any or each of those components and these components can be provided on either a standalone machine or, in some implementations, on multiple machines in a distributed system. The systems and methods described above can be implemented as a method, apparatus or article of manufacture using programming or engineering techniques to produce software, firmware, hardware, or any combination thereof. In addition, the systems and methods described above can be provided as one or more computer-readable programs embodied on or in one or more articles of manufacture. The term “article of manufacture” as used herein is intended to encompass code or logic accessible from and embedded in one or more computer-readable devices, firmware, programmable logic, memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g., integrated circuit chip, Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), etc.), electronic devices, a computer readable non-volatile storage unit (e.g., CD-ROM, floppy disk, hard disk drive, etc.). The article of manufacture can be accessible from a file server providing access to the computer-readable programs via a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc. The article of manufacture can be a flash memory card or a magnetic tape. The article of manufacture can include hardware logic as well as software or programmable code embedded in a computer readable medium that is executed by a processor. In general, the computer-readable programs can be implemented in any programming language, such as LISP, PERL, C, C++, C#, PROLOG, or in any byte code language such as JAVA. The software programs can be stored on or in one or more articles of manufacture as object code.

At least one aspect of this technical solution is directed to a system for generating a metric-based digital feed performance model, with a data processing system comprising memory and one or more processors to execute a participant microservice under a first authorization restriction, to obtain a participant object associated with a support service, execute a gateway microservice to determine whether the participant microservice satisfies the first authorization restriction, and in accordance with a determination that the participant microservice satisfies the first authorization restriction, authorize the participant microservice to obtain the participant object, execute an opportunity discovery microservice under a second authorization restriction, to obtain an opportunity object associated with the participant object, and to determine whether the opportunity object associated with the participant object satisfies an opportunity condition, in accordance with a determination that the opportunity object associated with the participant object satisfies the opportunity condition, execute the gateway microservice to authorize the opportunity discovery microservice to obtain the opportunity object, and determine whether the opportunity discovery microservice satisfies a third authorization restriction, and in accordance with a determination that the opportunity discovery microservice satisfies the third authorization restriction, authorize the opportunity discovery microservice to modify an opportunity object index at a participant system associated with the participant object.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to execute an import microservice under a fourth authorization restriction, to obtain, from a health data processing system, a support record associated with the participant identifier and the support service, where the participant object is associated with a support service and a support account.

At least one aspect of this technical solution is directed to a system where the health data processing system is a pharmaceutical data processing system, and the support record is a pharmaceutical prescription record.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to execute a prescription microservice to generate a transaction value associated with the pharmaceutical prescription record and the support account.

At least one aspect of this technical solution is directed to a system where the health data processing system is a health care provider data processing system, and the support record is a health care provider program record.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to execute an account microservice to modify a financial contribution to a support account associated with the support service and the participant identifier.

At least one aspect of this technical solution is directed to a system of claim 6, wherein the data processing system is further configured to execute an attachment microservice to generate a link between the participant object and the support account.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to execute the gateway microservice to configure at least one of the first authorization restriction, the second authorization restriction, the third authorization restriction, and the fourth authorization restriction.

At least one aspect of this technical solution is directed to a system where the data processing system is further configured to execute the gateway microservice to apply a security token associated with the third security restriction, wherein the determination that the participant microservice satisfies the first authorization restriction can include validating the security token.

At least one aspect of this technical solution is directed to a method for generating a metric-based digital feed performance model, by, obtaining, by a participant microservice under a first authorization restriction, a participant object associated with a support service, determining, by a gateway microservice, whether the participant microservice satisfies the first authorization restriction, authorizing the participant microservice to obtain the participant object, in accordance with a determination that the participant microservice satisfies the first authorization restriction, obtaining, by an opportunity discovery microservice under a second authorization restriction, an opportunity object associated with the participant object, determining, by the opportunity discovery microservice under the second authorization restriction, whether the opportunity object associated with the participant object satisfies an opportunity condition, authorizing, by the gateway microservice, the opportunity discovery microservice to obtain the opportunity object, in accordance with a determination that the opportunity object associated with the participant object satisfies the opportunity condition, determining, by the gateway microservice, whether the opportunity discovery microservice satisfies a third authorization restriction, and authorizing the opportunity discovery microservice to modify an opportunity object index at a participant system associated with the participant object, in accordance with a determination that the opportunity discovery microservice satisfies the third authorization restriction.

At least one aspect of this technical solution is directed to a method of including obtaining, by an import microservice under a fourth authorization restriction, from a health data processing system, a support record associated with the participant identifier and the support service, wherein the participant object is associated with a support service and a support account.

At least one aspect of this technical solution is directed to a method where the health data processing system is a pharmaceutical data processing system, and the support record is a pharmaceutical prescription record.

At least one aspect of this technical solution is directed to a method including generating, by a prescription microservice, a transaction value associated with the pharmaceutical prescription record and the support account.

At least one aspect of this technical solution is directed to a method where the health data processing system is a health care provider data processing system, and the support record is a health care provider program record.

At least one aspect of this technical solution is directed to a method including modifying, by an account microservice, a financial contribution to a support account associated with the support service and the participant identifier.

At least one aspect of this technical solution is directed to a method including generating, by an attachment microservice, a link between the participant object and the support account.

At least one aspect of this technical solution is directed to a system including configuring, by the gateway microservice, at least one of the first authorization restriction, the second authorization restriction, the third authorization restriction, and the fourth authorization restriction.

At least one aspect of this technical solution is directed to a system including the data processing system is further configured to applying, by the gateway microservice, a security token associated with the third security restriction, wherein the determination that the participant microservice satisfies the first authorization restriction can include validating the security token.

At least one aspect of this technical solution is directed to a computer readable medium with one or more instructions stored thereon and executable by a processor to execute a participant microservice under a first authorization restriction, to obtain a participant object associated with a support service, execute a gateway microservice to determine whether the participant microservice satisfies the first authorization restriction, and in accordance with a determination that the participant microservice satisfies the first authorization restriction, authorize the participant microservice to obtain the participant object, execute an opportunity discovery microservice under a second authorization restriction, to obtain an opportunity object associated with the participant object, and to determine whether the opportunity object associated with the participant object satisfies an opportunity condition, in accordance with a determination that the opportunity object associated with the participant object satisfies the opportunity condition, execute the gateway microservice to authorize the opportunity discovery microservice to obtain the opportunity object, and determine whether the opportunity discovery microservice satisfies a third authorization restriction, and in accordance with a determination that the opportunity discovery microservice satisfies the third authorization restriction, authorize the opportunity discovery microservice to modify an opportunity object index at a participant system associated with the participant object.

At least one aspect of this technical solution is directed to a computer readable medium where the computer readable medium further can include one or more instructions executable by a processor to execute an account microservice to modify a financial contribution to a support account associated with the support service and the participant identifier.

The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are illustrative, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable,” to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components

With respect to the use of plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.).

Although the figures and description may illustrate a specific order of method steps, the order of such steps may differ from what is depicted and described, unless specified differently above. Also, two or more steps may be performed concurrently or with partial concurrence, unless specified differently above. Such variation may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations of the described methods could be accomplished with standard programming techniques with rule-based logic and other logic to accomplish the various connection steps, processing steps, comparison steps, and decision steps.

It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation, no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations).

Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general, such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”

Further, unless otherwise noted, the use of the words “approximate,” “about,” “around,” “substantially,” etc., mean plus or minus ten percent.

The foregoing description of illustrative implementations has been presented for purposes of illustration and of description. It is not intended to be exhaustive or limiting with respect to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the disclosed implementations. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents. 

What is claimed is:
 1. A system to present opportunities from third-party applications, comprising: a data processing system comprising memory operatively coupled to one or more hardware processors to: identify, via an interface of the data processing system, a third-party application of a plurality of third-party applications configured with application programming interfaces (“APIs”) compatible with the interface of the data processing system; transmit, to the third-party application, a query constructed based on a template that is compatible with an API of the third-party application; receive, responsive to the query, a response from the third-party application comprising an opportunity event and a participant profile object, the participant profile object being linked with the participant object and generated in response to importing participant information from a third-party administrator device; select a participant object that satisfies one or more parameters associated with the opportunity event; and provide, to a computing device linked with the participant object, an indication of the opportunity event.
 2. The system of claim 1, wherein the data processing system is further configured to: determine to query the third-party application responsive to a trigger condition.
 3. The system of claim 1, wherein the data processing system is further configured to: crawl a web page associated with a provider of the third-party application; and determine, responsive to the crawl of the web page, to query the third-party application responsive to identifying a candidate opportunity on the web page of the provider associated with the third-party application.
 4. The system of claim 1, wherein the data processing system is further configured to: determine, based on a location of the computing device linked with the participant object, to transmit the query to the third-party application.
 5. The system of claim 1, wherein the data processing system is further configured to: train a machine learning model with historical data associated with opportunities provided by third-party applications; determine, based on information associated with the participant object input into the machine learning model, to transmit the query to the third-party application based on an output of the machine learning model.
 6. The system of claim 1, wherein the data processing system is further configured to: identify a second third-party application different from the third-party application; select a second template different than the template, the second template compatible with a second API of the second third-party application that is different than the API of the third-party application; and construct a second query for opportunities based on the second template.
 7. The system of claim 1, wherein the data processing system is further configured to: construct the query with credentials authorizing the data processing system to receive the response with the opportunity event.
 8. The system of claim 7, wherein the credentials correspond to the participant object.
 9. The system of claim 1, wherein the data processing system is further configured to: parse the response to identify the opportunity event; construct an opportunity object to provide to the computing device based on the identified opportunity event; and transmit the opportunity object for presentation via the computing device.
 10. The system of claim 9, wherein the data processing system is further configured to: receive, responsive to transmission of the opportunity object, an indication to execute the opportunity object; and authorize, responsive to the indication, the opportunity object for execution by the participant object.
 11. A method of presenting opportunities from third-party applications, comprising: identifying, by a data processing system comprising one or more processors via an interface of the data processing system, a third-party application of a plurality of third-party applications configured with application programming interfaces (“APIs”) compatible with the interface of the data processing system; transmitting, by the data processing system to the third-party application, a query constructed based on a template that is compatible with an API of the third-party application; receiving, by the data processing system responsive to the query, a response from the third-party application comprising an opportunity event and a participant profile object, the participant profile object being linked with the participant object and generated in response to importing participant information from a third-party administrator device; selecting, by the data processing system, a participant object that satisfies one or more parameters associated with the opportunity event; and providing, by the data processing system to a computing device linked with the participant object, an indication of the opportunity event.
 12. The method of claim 11, comprising: determining, by the data processing system, to query the third-party application responsive to a trigger condition.
 13. The method of claim 11, comprising: crawling, by the data processing system, a web page associated with a provider of the third-party application; and determining, by the data processing system responsive to the crawl of the web page, to query the third-party application responsive to identifying a candidate opportunity on the web page of the provider associated with the third-party application.
 14. The method of claim 11, comprising: determining, by the data processing system based on a location of the computing device linked with the participant object, to transmit the query to the third-party application.
 15. The method of claim 11, comprising: training, by the data processing system, a machine learning model with historical data associated with opportunities provided by third-party applications; determining, by the data processing system based on information associated with the participant object input into the machine learning model, to transmit the query to the third-party application based on an output of the machine learning model.
 16. The method of claim 11, comprising: identifying, by the data processing system, a second third-party application different from the third-party application; selecting, by the data processing system, a second template different than the template, the second template compatible with a second API of the second third-party application that is different than the API of the third-party application; and constructing, by the data processing system, a second query for opportunities based on the second template.
 17. The method of claim 11, comprising: constructing, by the data processing system, the query with credentials authorizing the data processing system to receive the response with the opportunity event.
 18. The method of claim 17, wherein the credentials correspond to the participant object.
 19. The method of claim 11, comprising: parsing, by the data processing system, the response to identify the opportunity event; constructing, by the data processing system, an opportunity object to provide to the computing device based on the identified opportunity event; and transmitting, by the data processing system, the opportunity object for presentation via the computing device.
 20. The method of claim 19, comprising: receiving, by the data processing system responsive to transmission of the opportunity object, an indication to execute the opportunity object; and authorizing, by the data processing system responsive to the indication, the opportunity object for execution by the participant object. 